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

agent tool_use skill risk: medium

Census Bureau Automation via Rube MCP

Provides step-by-step instructions for automating Census Bureau operations using Composio's census_bureau toolkit through Rube MCP, including prerequisites, tool discovery with RUB…

  • Policy sensitive
  • Human review
  • External action: high

SKILL 1 file

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

Automate Census Bureau operations through Composio's Census Bureau toolkit via Rube MCP.

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

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["census_bureau"]
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 Census Bureau-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `census_bureau` |
| 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
  • census_bureau toolkit connection status

OPTIONAL CONTEXT

  • specific use_case for tool search
  • existing session_id

TOOLS REQUIRED

  • RUBE_SEARCH_TOOLS
  • RUBE_MANAGE_CONNECTIONS
  • RUBE_MULTI_EXECUTE_TOOL
  • RUBE_GET_TOOL_SCHEMAS
  • RUBE_REMOTE_WORKBENCH

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. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
  5. If connection is not ACTIVE, follow the returned auth link to complete setup
  6. Confirm connection status shows ACTIVE before running any 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
  • always call RUBE_SEARCH_TOOLS first
  • verify ACTIVE connection before execution
  • reuse session IDs within workflow

SUCCESS CRITERIA

  • Verify Rube MCP connection before use
  • Activate Census Bureau connection via RUBE_MANAGE_CONNECTIONS
  • Always discover tools with RUBE_SEARCH_TOOLS first
  • Execute only schema-compliant tool calls
  • Reuse session IDs within workflows

FAILURE MODES

  • Hardcoding tool slugs without searching first
  • Executing tools before confirming ACTIVE connection
  • Omitting the memory parameter in RUBE_MULTI_EXECUTE_TOOL
  • Failing to handle pagination tokens

CAVEATS

Dependencies
  • Rube MCP connection (RUBE_SEARCH_TOOLS available)
  • Active Census Bureau connection via RUBE_MANAGE_CONNECTIONS
Missing context
  • Target MCP client or environment
  • Example task inputs and expected outputs
Ambiguities
  • Exact expected format and parameters for RUBE_* function calls are shown inconsistently between prose and code blocks
  • Does not specify how to handle errors or failed tool executions

QUALITY

OVERALL
0.76
CLARITY
0.82
SPECIFICITY
0.88
REUSABILITY
0.65
COMPLETENESS
0.78

IMPROVEMENT SUGGESTIONS

  • Add a minimal end-to-end example with a concrete Census task (e.g., 'fetch population data for state X')
  • Define the precise JSON schema or argument shapes expected by each RUBE_* call instead of prose descriptions

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