Skip to main content
Glama

Handover Accept

handover_accept
Idempotent

Accepts and picks up a handover by ID or resume code, returns its full saved state and private continuation thread, and records a receipt. Agent pickup is not client approval; the client decision remains pending. Do not generate client tokens. Free, no quota; picking up is always free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "handover_accept"
  }
}

Input Schema

NameRequiredDescriptionDefault
_refNoOptional handover referral ID from your install link.
tokenNoOptional client capability token from the recipient link; it is not the creator's owner key.
_zambo_keyNoOptional opaque Zambo access capability. Never place it in a URL or public log.
agent_nameNoOptional self-reported name of the AI receiving the handover.
_session_idNoOptional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together.
handover_idNoHandover ID, if available.
resume_codeNoResume code from the handover, if an ID is unavailable.
client_tokenNoAlias for token: the recipient's client capability, not the owner token.
_caller_labelNoOptional caller label recorded as a caller-reported claim in the receipt.zambo-starter
_caller_handleNoOpaque anonymous continuity handle returned during initialize. Reuse it across MCP sessions; it is not payment authorization.
receipt_visibilityNoReceipt visibility for this call. Public is the default. Private returns a bearer link; anyone with that link can read it, so keep it secret. The raw token is not stored.public
_continuity_ai_labelNoOptional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client.

Output Schema

NameRequiredDescriptionDefault
okYes
idsYes
nextNo
tierNo
urlsYes
errorNo
graphNo
activeNo
resultYesThe tool's observed JSON value or plain-text result.
intentsNo
next_upNo
paymentNo
day_passNo
today_urlNo
expires_atNo
human_lineYes
next_stepsNo
daily_recapNo
renew_nudgeNo
unlock_linkNo
seconds_leftNo
resume_statusNo
resumed_resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / receipt_visibility
      Added value: +{
      +  "default": "public",
      +  "description": "Receipt visibility for this call. Public is the default. Private returns a bearer link; anyone with that link can read it, so keep it secret. The raw token is not stored.",
      +  "enum": [
      +    "public",
      +    "private"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "result",
      -  "ok",
      -  "human_line",
      -  "next",
      -  "ids",
      -  "urls"
      -]New value: +[
      +  "result",
      +  "ok",
      +  "human_line",
      +  "ids",
      +  "urls"
      +]
  2. Changed8 schema fields changed
    • changedOutput schema / properties / daily_recap / type
      Previous value: -"object"New value: +[
      +  "object",
      +  "null"
      +]
    • changedOutput schema / properties / error / anyOf
      Previous value: -[
      -  {
      -    "required": [
      -      "next_call"
      -    ]
      -  },
      -  {
      -    "required": [
      -      "next_url"
      -    ]
      -  }
      -]New value: +[
      +  {
      +    "properties": {
      +      "next_call": {}
      +    },
      +    "required": [
      +      "next_call"
      +    ]
      +  },
      +  {
      +    "properties": {
      +      "next_url": {}
      +    },
      +    "required": [
      +      "next_url"
      +    ]
      +  }
      +]
    • addedOutput schema / properties / graph / properties / edges
      Added value: +{
      +  "items": {
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / graph / properties / nodes
      Added value: +{
      +  "items": {
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / graph / properties / retries
      Added value: +{
      +  "properties": {
      +    "max": {
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "used": {
      +      "minimum": 0,
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "used",
      +    "max"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / graph / properties / sources
      Added value: +{
      +  "properties": {
      +    "not_checked": {
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "not_resolved": {
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "resolved": {
      +      "minimum": 0,
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "resolved",
      +    "not_resolved",
      +    "not_checked"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / graph / properties / summary
      Added value: +{
      +  "type": "string"
      +}
    • removedOutput schema / properties / next_steps / minItems
      Removed value: -1
  3. Changed1 schema field changed
    • changedOutput schema / properties / human_line / maxLength
      Previous value: -200New value: +512
  4. Changed2 schema fields changed
    • addedInput schema / properties / agent_name / description
      Added value: +"Optional self-reported name of the AI receiving the handover."
    • addedInput schema / properties / token / description
      Added value: +"Optional client capability token from the recipient link; it is not the creator's owner key."
  5. Changed3 schema fields changed
    • addedInput schema / properties / handover_id / description
      Added value: +"Handover ID, if available."
    • addedInput schema / properties / resume_code
      Added value: +{
      +  "description": "Resume code from the handover, if an ID is unavailable.",
      +  "type": "string"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "handover_id"
      -]
  6. Changed2 schema fields changed
    • addedInput schema / properties / _caller_handle
      Added value: +{
      +  "description": "Opaque anonymous continuity handle returned during initialize. Reuse it across MCP sessions; it is not payment authorization.",
      +  "maxLength": 64,
      +  "type": "string"
      +}
    • addedInput schema / properties / _caller_label / default
      Added value: +"zambo-starter"
  7. Changed1 schema field changed
    • changedOutput schema / properties / graph / properties / aer / const
      Previous value: -"draft-zambo-aer1-25"New value: +"draft-zambo-aer1-26"
  8. Changed1 schema field changed
    • changedOutput schema / properties / graph / properties / aer / const
      Previous value: -"draft-zambo-aer1-24"New value: +"draft-zambo-aer1-25"
  9. Changed1 schema field changed
    • changedOutput schema / properties / graph / properties / aer / const
      Previous value: -"draft-zambo-aer1-23"New value: +"draft-zambo-aer1-24"
  10. Changed1 schema field changed
    • changedOutput schema / properties / graph / properties / aer / const
      Previous value: -"draft-zambo-aer1-22"New value: +"draft-zambo-aer1-23"
  11. Changed1 schema field changed
    • changedOutput schema / properties / graph / properties / aer / const
      Previous value: -"draft-zambo-aer1-21"New value: +"draft-zambo-aer1-22"
  12. Changed1 schema field changed
    • changedOutput schema / properties / graph / properties / aer / const
      Previous value: -"draft-zambo-aer1-20"New value: +"draft-zambo-aer1-21"
  13. Changed2 schema fields changed
    • addedInput schema / properties / client_token
      Added value: +{
      +  "description": "Alias for token: the recipient's client capability, not the owner token.",
      +  "maxLength": 500,
      +  "type": "string"
      +}
    • addedOutput schema / properties / next_steps
      Added value: +{
      +  "items": {},
      +  "minItems": 1,
      +  "type": "array"
      +}
  14. Changed12 schema fields changed
    • addedInput schema / properties / _ref
      Added value: +{
      +  "description": "Optional handover referral ID from your install link.",
      +  "format": "uuid",
      +  "type": "string"
      +}
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +true
    • addedOutput schema / properties / error
      Added value: +{
      +  "additionalProperties": true,
      +  "anyOf": [
      +    {
      +      "required": [
      +        "next_call"
      +      ]
      +    },
      +    {
      +      "required": [
      +        "next_url"
      +      ]
      +    }
      +  ],
      +  "properties": {
      +    "code": {
      +      "type": "string"
      +    },
      +    "next_call": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "args": {
      +          "type": "object"
      +        },
      +        "tool": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "tool",
      +        "args"
      +      ],
      +      "type": "object"
      +    },
      +    "next_step": {
      +      "type": "string"
      +    },
      +    "next_url": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "code",
      +    "next_step"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / graph
      Added value: +{
      +  "properties": {
      +    "aer": {
      +      "const": "draft-zambo-aer1-20"
      +    },
      +    "schema": {
      +      "const": "zambo.graph/1"
      +    }
      +  },
      +  "required": [
      +    "schema",
      +    "aer",
      +    "nodes",
      +    "edges",
      +    "retries",
      +    "sources",
      +    "summary"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / human_line / maxLength
      Added value: +200
    • addedOutput schema / properties / human_line / pattern
      Added value: +"^[^\\r\\n]*$"
    • addedOutput schema / properties / ids
      Added value: +{
      +  "additionalProperties": {
      +    "type": "string"
      +  },
      +  "type": "object"
      +}
    • addedOutput schema / properties / next
      Added value: +{
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedOutput schema / properties / ok
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / renew_nudge
      Added value: +{
      +  "type": "object"
      +}
    • addedOutput schema / properties / urls
      Added value: +{
      +  "additionalProperties": {
      +    "type": "string"
      +  },
      +  "type": "object"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "result"
      -]New value: +[
      +  "result",
      +  "ok",
      +  "human_line",
      +  "next",
      +  "ids",
      +  "urls"
      +]
  15. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare non-read-only, idempotent, non-destructive, open-world; the description adds real value beyond that by disclosing the receipt side effect, the returned private continuation thread, the free/no-quota pricing, and the important semantic that pickup does not constitute client approval. This is consistent with readOnlyHint=false because a receipt is written.

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?

Three tight sentences: the action and return payload lead, then the critical approval caveat, then the cost reassurance. No filler, and the most consequential warning (no client tokens / not approval) is front-loaded rather than buried.

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?

An output schema exists, so return-value detail is not required, yet the description still names the payload composition (saved state plus continuation thread). With all parameters documented by the schema, the only remaining gap is the implicit requirement that at least one of handover_id or resume_code be supplied despite zero required params.

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 coverage is 100%, so each of the twelve parameters is already documented, and the description only echoes the ID/resume-code lookup pair. It adds no disambiguation of token vs client_token aliasing, which key fields bind a session, or what 'caller-reported claim' means for the receipt label — the schema carries that burden.

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 opens with a specific verb and resource: 'Accepts and picks up a handover by ID or resume code,' and enumerates the outcome (full saved state, private continuation thread, receipt). That differentiates it from list/status siblings, though it never names handover_status or handover explicitly to route the agent.

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?

It gives constraints ('Do not generate client tokens,' 'picking up is always free') and a conceptual caveat ('Agent pickup is not client approval'), which is implied usage guidance. However, it never states when to choose this over handover_status or handover, nor what happens if both handover_id and resume_code are omitted.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources