VibeTape MCP Server

Overview Schema Source Related Servers Discussions Admin

create_handoff_for_agent

Generate a LangGraph-compatible handoff payload to transfer a task between agents, including required context and optional token budget and failure history.

Instructions

Create a LangGraph-compatible handoff payload for agent-to-agent transfer

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": {
      "task_id": "<task_id>",
      "from_agent": "<from_agent>",
      "to_agent": "<to_agent>"
    },
    "name": "create_handoff_for_agent"
  }
}

Input Schema

Name	Required	Description
`task_id`	Yes	Task ID being handed off
`to_agent`	Yes	Actor ID of target agent
`from_agent`	Yes	Actor ID of source agent
`budget_tokens`	No	Token budget for context (default: 500)
`include_retex`	No	Include relevant RETEX (default: true)
`include_failures`	No	Include recent failures (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Aug 1, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only states what the tool creates, without mentioning side effects, return values, permissions, or any other behavioral traits. This is insufficient for a tool with no other behavioral metadata.

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?

The description is a single, focused sentence that immediately states the tool's purpose. It is front-loaded and contains no filler or redundant information.

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

Completeness2/5

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

Despite the full parameter schema coverage, the description lacks essential context: no return value information, no explanation of how the handoff payload is used, and no differentiation from similar tools. Since there is no output schema, the description should have compensated with more detail, but it does not.

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

Parameters3/5

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

The input schema has 100% description coverage for all 6 parameters, so the schema itself fully documents parameter meanings. The description adds no additional parameter-level semantics, keeping the score at the baseline of 3.

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

Purpose4/5

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

The description states 'Create a LangGraph-compatible handoff payload for agent-to-agent transfer,' which clearly identifies the verb (create), resource (handoff payload), and scope (agent-to-agent transfer). However, it does not distinguish this tool from sibling 'generate_context_handoff', which appears to serve a similar purpose.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like generate_context_handoff or suggest_transition_card. There are no usage contexts, exclusions, or prerequisites mentioned.

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