Skip to main content
Glama

Hand Off Context to Specialist Wing

handoff_to_agent

Transfers task context, architectural findings, and selected memory IDs between specialist agent wings so work continues without losing constraints.

Instructions

Hand off task context, architectural findings, and selected memory IDs from one specialist agent wing to another.

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": {
      "summary": "<summary>"
    },
    "name": "handoff_to_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoOptional actionable task for the target wing.
wingNoTarget specialist wing (alias: to_wing).
filesNoOptional list of relevant file paths.
summaryYesConcise summary of findings and constraints.
to_wingNoTarget specialist wing.
from_wingNoOriginating specialist wing.
namespaceNoProject or workspace namespace.
from_agentNoOriginating agent or wing identifier.
memory_idsNoOptional list of memory IDs to attach to the handoff.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the bar is lower. The description adds that memory IDs and findings are transferred to a target wing, which is useful context about effect, but it never says whether the handoff is persisted, delivered synchronously, what happens on a duplicate call (notably relevant given idempotentHint=false), or what the caller receives back.

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?

A single front-loaded sentence with no filler; the verb and direction lead. It is efficiently written, though the terseness comes at the cost of the usage and behavioral detail a nine-parameter mutation tool warrants.

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?

For a non-idempotent nine-parameter mutation with no output schema, the description is too thin: it omits the return/confirmation behavior (which no output schema covers), the alias ambiguity between `wing` and `to_wing`, and defaulting for origin fields. An agent could invoke it, but not confidently predict the result.

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?

Schema description coverage is 100%, so every one of the nine parameters is already documented in the schema, including the wing enums. The description adds no meaning beyond that — it does not explain the duplicated `wing`/`to_wing` alias, whether `from_wing` or `from_agent` is inferred, or how `memory_ids` are validated. Baseline 3 applies.

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 gives a specific verb ('Hand off') and enumerates the payload ('task context, architectural findings, and selected memory IDs') plus the direction ('from one specialist agent wing to another'). That is enough for an agent to distinguish this from memory-oriented siblings such as recall_memories or build_context, though it never explicitly names an alternative.

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

Usage Guidelines3/5

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

Usage is only implied by the act of handing off between wings; there is no statement of when an agent should hand off versus build or recall context itself, no prerequisites (does the target wing need to exist or be active?), and no conditions under which not to call it. The absence of any alternative routing leaves the agent to infer the trigger.

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