Skip to main content
Glama

hand_off

Destructive

Transfers a task card to another team agent in one step: assigns it, moves it to todo, records a comment, and releases your checkout. Use when another agent must do the next part.

Instructions

Give the card to another agent who must do the next part: assigns it to them, moves it to todo, writes the comment, cancels your active wait and releases your checkout, in one step instead of assign + move + release. The addressee must be an agent of the team directory. Use ask_agent when you only need their answer and keep the card.

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>",
      "to": "<to>",
      "why": "<why>"
    },
    "name": "hand_off"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesAgent name or UUID from get_team_directory who takes the card.
whyYesWhat they must do and what is already done, max 4000 chars.
task_idYesThe card to hand over (UUID or 6-12 hex short id).
turn_idNoOptional turn id within the session (max 200 chars), copied onto the outcome.
session_idNoOptional runner session id (max 200 chars), copied onto the recorded outcome and wait.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.7

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already flag destructive=true, idempotent=false, readOnly=false; the description goes further by naming exactly which state is destroyed or changed – your active wait is cancelled and your checkout released, the card is reassigned and moved to todo. It stops short of saying those effects are irreversible or what happens if the target agent is invalid, but the disclosure beyond annotations is substantial.

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?

Two sentences, front-loaded with the action and its composite effects, with the alternative relegated to the second sentence. The opening sentence is long with five stacked clauses, but each clause adds a distinct effect rather than restating the name.

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

Completeness3/5

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

For a five-parameter composite mutation with no output schema, the description covers effects and the alternative well, but says nothing about failure modes (unknown or unavailable agent), whether the handover can be undone, or what the caller observes on success. Adequate but with clear gaps.

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?

With 100% schema coverage the baseline is 3, and the description adds real meaning: the 'why' parameter is what gets written as the comment, and 'to' must resolve against the team directory. turn_id and session_id are not addressed, keeping it off a 5.

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?

States a specific action on a specific resource (hand a card to another agent) and enumerates the composite effects: assigns, moves to todo, writes the comment, cancels the active wait, releases the checkout. It also contrasts itself with ask_agent, so an agent can distinguish it from siblings without opening schemas.

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?

Gives an explicit when-to-use rule ('another agent who must do the next part'), a prerequisite ('the addressee must be an agent of the team directory'), and an explicit alternative with its selecting condition ('Use ask_agent when you only need their answer and keep the card').

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