Skip to main content
Glama
felkru

handoff-mcp

by felkru

handoff

Send a coding task to a separate agent (Codex or Antigravity) for independent execution and return the result.

Instructions

Hand a task off to a peer coding-agent CLI and return its answer (blocking).

Use this for tasks that finish in a few minutes. For long/agentic work,
prefer `handoff_start` + `handoff_status` so you get progress and don't block.

Choosing a backend (see `handoff_guidance` for detail):
  - `codex` (OpenAI): code review, bug hunting, refactors, terminal-agentic
    work, second opinion on code/text. Text & images (not PDFs).
  - `antigravity` (Google Gemini 3): visual feedback (screenshots, diagrams,
    PDFs), very-long-context reads (whole repos / huge docs), cheap bulk.

Hand off aggressively when the Claude/Fable usage limit is close — each
backend bills to a separate subscription pool.

Args:
    prompt: What to do. The peer agent has NONE of this conversation's
        context — be explicit and self-contained.
    backend: "codex" or "antigravity".
    files: Absolute/~ paths to attach. codex: text + images. antigravity:
        text, images, and PDFs.
    model: Optional model id override; empty = the CLI's own default
        (e.g. "gpt-5.3-codex", "gemini-3.1-pro-preview").
    cwd: A project directory the agent may read for extra context. The
        process itself runs in a throwaway temp dir; originals are never
        modified unless you set `approve=True`.
    approve: Allow the agent to actually make edits (codex: workspace-write
        sandbox; antigravity: --dangerously-skip-permissions). Default False
        = read-only, right for reviews/opinions.
    timeout: Seconds before abort.

Returns:
    The peer agent's response, or a clear "[handoff error] …" string.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNo
filesNo
modelNo
promptYes
approveNo
backendYes
timeoutNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided, so description covers blocking behavior, temp directory usage, no originals modifications without approval, and return value format. It also clarifies the peer agent has no conversation context.

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

Conciseness4/5

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

Description is well-structured with clear sections but slightly verbose. Front-loads purpose and main guidelines. Each sentence adds value, though could be trimmed for brevity.

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 purpose, usage, parameters, behavioral effects, and return value. References sibling tools. However, could include example of error handling or more detail on output schema structure.

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

Parameters5/5

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

Schema description coverage is 0%, but description explains all 7 parameters with meaningful details (e.g., file type support per backend, default behaviors for approve, timeout meaning). Adds value beyond schema types.

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?

Description clearly states 'Hand a task off to a peer coding-agent CLI' and distinguishes from sibling tools like handoff_start by noting blocking vs non-blocking. It also specifies when to use each sibling.

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?

Explicitly says 'Use this for tasks that finish in a few minutes. For long/agentic work, prefer handoff_start + handoff_status'. Also provides guidance on backend selection and aggressive handoff when usage limit is close.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/felkru/handoff-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server