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

agent tool_use skill risk: medium

Coupa Automation via Rube MCP

Instructs the model to automate Coupa operations through Composio's Coupa toolkit via Rube MCP by first searching tools, managing connections, and executing discovered tools follow…

  • Policy sensitive
  • Human review
  • External action: high

SKILL 1 file

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

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

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

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Coupa connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `coupa`
- 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 `coupa`
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: "Coupa 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 Coupa task"}]
session: {id: "existing_session_id"}
```

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["coupa"]
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 Coupa-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `coupa` |
| 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 MCP connection
  • active Coupa connection via RUBE_MANAGE_CONNECTIONS

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. Always discover available tools before executing workflows
  4. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
  5. Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
  6. Use exact field names and types from the search results
  7. Always include memory in RUBE_MULTI_EXECUTE_TOOL calls even if empty
  8. Reuse session IDs within a workflow
  9. Generate new session IDs for new workflows
  10. Check responses for pagination tokens and continue fetching until complete

EXPECTED OUTPUT

Format
markdown
Constraints
  • include prerequisites, setup steps, tool discovery pattern, core workflow, known pitfalls, and quick reference table

SUCCESS CRITERIA

  • Verify Rube MCP availability via RUBE_SEARCH_TOOLS
  • Confirm Coupa connection status is ACTIVE
  • Use schema-compliant arguments from search results

FAILURE MODES

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

EXAMPLES

Includes multiple example RUBE_* tool calls showing queries, arguments, and session usage for discovery, connection, and execution.

CAVEATS

Dependencies
  • Rube MCP connection (RUBE_SEARCH_TOOLS available)
  • Active Coupa connection via RUBE_MANAGE_CONNECTIONS
Missing context
  • Target AI model/client capabilities
  • Example concrete Coupa task to demonstrate full flow
Ambiguities
  • Does not specify desired output format or success criteria for completed workflows.

QUALITY

OVERALL
0.82
CLARITY
0.85
SPECIFICITY
0.90
REUSABILITY
0.80
COMPLETENESS
0.75

IMPROVEMENT SUGGESTIONS

  • Replace the placeholder "your specific Coupa task" with an explicit input variable such as {{task_description}}.
  • Add a required final step that summarizes results or returns structured JSON after tool execution.

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