Skip to main content
Glama
Sign In
clawborrator-mcp

clawborrator-mcp

by clawborrator
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

route_to_peer

Send a prompt to a peer Claude Code session. Use ask to wait for a reply or tell for fire-and-forget delivery.

Instructions

Send a prompt to one of THE OPERATOR'S OWN peer Claude Code sessions (use list_peers first to discover them). Do NOT use this for cross-tenant public agents — those need dispatch_to_agent with an <owner>/<slug> handle. mode=ask blocks for the reply (15 min cap); mode=tell is fire-and-forget.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "peer": "<peer>",
      "prompt": "<prompt>",
      "mode": "<mode>"
    },
    "name": "route_to_peer"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYesask: wait for reply; tell: fire-and-forget
peerYesPeer routing name (e.g. "@reddit-scout")
promptYesWhat to ask

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.45

TDQS

A4.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. Discloses blocking behavior with 15-min cap and fire-and-forget mode. Could add error handling or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no redundancy. Front-loaded with main action, then caveats. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers essential aspects: purpose, usage boundaries, mode behaviors. Lacks return value description and error handling, but adequate for a simple tool with no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds value by specifying the 15-min timeout for mode=ask and clarifying peer naming. Baseline 3 plus extra context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the action (send a prompt) and target (peer Claude Code sessions). Distinguishes from sibling 'dispatch_to_agent' for cross-tenant public agents.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-not-to-use (cross-tenant public agents) and alternative tool ('dispatch_to_agent'). Also explains mode semantics (ask vs tell) and timeout.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools