Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts Appointo Rube MCP Automation Guide

agent operations skill risk: medium

Appointo Rube MCP Automation Guide

Instructs the model to automate Appointo operations via Composio's toolkit through Rube MCP by first calling RUBE_SEARCH_TOOLS, verifying ACTIVE connections with RUBE_MANAGE_CONNEC…

  • External action: high

SKILL 1 file

SKILL.md
---
name: appointo-automation
description: "Automate Appointo tasks via Rube MCP (Composio). Always search tools first for current schemas."
---
# Appointo Automation via Rube MCP

Automate Appointo operations through Composio's Appointo toolkit via Rube MCP.

**Toolkit docs**: [composio.dev/toolkits/appointo](https://composio.dev/toolkits/appointo)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Appointo connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `appointo`
- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas

## Setup

**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `appointo`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. Confirm connection status shows ACTIVE before running any workflows

## Tool Discovery

Always discover available tools before executing workflows:

```
RUBE_SEARCH_TOOLS
queries: [{use_case: "Appointo operations", known_fields: ""}]
session: {generate_id: true}
```

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

## Core Workflow Pattern

### Step 1: Discover Available Tools

```
RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Appointo task"}]
session: {id: "existing_session_id"}
```

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["appointo"]
session_id: "your_session_id"
```

### Step 3: Execute Tools

```
RUBE_MULTI_EXECUTE_TOOL
tools: [{
  tool_slug: "TOOL_SLUG_FROM_SEARCH",
  arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"
```

## Known Pitfalls

- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS`
- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools
- **Schema compliance**: Use exact field names and types from the search results
- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`)
- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows
- **Pagination**: Check responses for pagination tokens and continue fetching until complete

## Quick Reference

| Operation | Approach |
|-----------|----------|
| Find tools | `RUBE_SEARCH_TOOLS` with Appointo-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `appointo` |
| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs |
| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` |
| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` |

---
*Powered by [Composio](https://composio.dev)*

REQUIRED CONTEXT

  • RUBE_SEARCH_TOOLS availability
  • Appointo connection status via RUBE_MANAGE_CONNECTIONS

OPTIONAL CONTEXT

  • specific Appointo use case
  • existing session_id

TOOLS REQUIRED

  • RUBE_SEARCH_TOOLS
  • RUBE_MANAGE_CONNECTIONS
  • RUBE_MULTI_EXECUTE_TOOL
  • RUBE_REMOTE_WORKBENCH
  • RUBE_GET_TOOL_SCHEMAS

ROLES & RULES

  1. Always search tools first for current schemas
  2. Always call RUBE_SEARCH_TOOLS first to get current tool schemas
  3. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
  4. Call RUBE_MANAGE_CONNECTIONS with toolkit appointo
  5. Confirm connection status shows ACTIVE before running any workflows
  6. Always discover available tools before executing workflows
  7. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
  8. Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
  9. Use exact field names and types from the search results
  10. Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
  11. Reuse session IDs within a workflow
  12. Generate new session IDs for new workflows
  13. Check responses for pagination tokens and continue fetching until complete

EXPECTED OUTPUT

Format
markdown
Constraints
  • include setup steps
  • always search tools first
  • use exact schemas from search results

SUCCESS CRITERIA

  • Always discover tools before executing
  • Verify active Appointo connection
  • Use schema-compliant arguments from search results
  • Follow the three-step core workflow pattern

FAILURE MODES

  • Hardcoding tool slugs without first calling RUBE_SEARCH_TOOLS
  • Executing tools before confirming ACTIVE connection status
  • Omitting the memory parameter in RUBE_MULTI_EXECUTE_TOOL
  • Failing to reuse or correctly manage session IDs

EXAMPLES

Includes three example tool-call blocks (RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, RUBE_MULTI_EXECUTE_TOOL) plus a quick-reference table.

CAVEATS

Dependencies
  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Appointo connection via RUBE_MANAGE_CONNECTIONS
Missing context
  • Concrete examples of Appointo operations or use cases
  • Expected response formats or success criteria for tool calls
Ambiguities
  • Placeholder 'your specific Appointo task' is generic and undefined.
  • Session ID reuse rules are stated but lack concrete multi-step examples.

QUALITY

OVERALL
0.76
CLARITY
0.82
SPECIFICITY
0.68
REUSABILITY
0.78
COMPLETENESS
0.74

IMPROVEMENT SUGGESTIONS

  • Replace generic use-case placeholders with 2-3 concrete examples such as 'create booking' or 'list appointments'.
  • Add a minimal end-to-end example workflow with sample tool slugs and arguments.

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR AGENT