Zambo

Handover Status

handover_status

Read-onlyIdempotent

Checks a handover by ID or resume code, including pickup status and the separate client decision/release hint. Agent pickup alone does not authorize payment release. AER-1 receipt, verifiable offline.

Input Schema

Name	Required	Description	Default
`_ref`	No	Optional handover referral ID from your install link.
`_zambo_key`	No	Optional opaque Zambo access capability. Never place it in a URL or public log.
`_session_id`	No	Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together.
`handover_id`	No	Handover ID, if available.
`resume_code`	No	Resume code from the handover, if an ID is unavailable.
`_caller_label`	No	Optional caller label recorded as a caller-reported claim in the receipt.	zambo-starter
`_caller_handle`	No	Opaque anonymous continuity handle returned during initialize. Reuse it across MCP sessions; it is not payment authorization.
`_continuity_ai_label`	No	Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client.

Output Schema

Name	Required	Description
`ok`	Yes
`ids`	Yes
`next`	Yes
`tier`	No
`urls`	Yes
`error`	No
`graph`	No
`active`	No
`result`	Yes	The tool's observed JSON value or plain-text result.
`intents`	No
`next_up`	No
`payment`	No
`day_pass`	No
`today_url`	No
`expires_at`	No
`human_line`	Yes
`next_steps`	No
`daily_recap`	No
`renew_nudge`	No
`unlock_link`	No
`seconds_left`	No
`resume_status`	No
`resumed_result`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026
- changedOutput schema / properties / human_line / maxLength
```
Previous value: -200New value: +512
```

Changed3 schema fields changedNov 1, 2026

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"
-]
```

Changed2 schema fields changedOct 25, 2026

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"
```

Changed1 schema field changedOct 23, 2026
- changedOutput schema / properties / graph / properties / aer / const
```
Previous value: -"draft-zambo-aer1-25"New value: +"draft-zambo-aer1-26"
```
Changed1 schema field changedOct 22, 2026
- changedOutput schema / properties / graph / properties / aer / const
```
Previous value: -"draft-zambo-aer1-24"New value: +"draft-zambo-aer1-25"
```
Changed1 schema field changedOct 20, 2026
- changedOutput schema / properties / graph / properties / aer / const
```
Previous value: -"draft-zambo-aer1-23"New value: +"draft-zambo-aer1-24"
```
Changed1 schema field changedOct 19, 2026
- changedOutput schema / properties / graph / properties / aer / const
```
Previous value: -"draft-zambo-aer1-22"New value: +"draft-zambo-aer1-23"
```
Changed1 schema field changedOct 18, 2026
- changedOutput schema / properties / graph / properties / aer / const
```
Previous value: -"draft-zambo-aer1-21"New value: +"draft-zambo-aer1-22"
```
Changed1 schema field changedOct 18, 2026
- changedOutput schema / properties / graph / properties / aer / const
```
Previous value: -"draft-zambo-aer1-20"New value: +"draft-zambo-aer1-21"
```
Changed1 schema field changedOct 17, 2026
- addedOutput schema / properties / next_steps
```
Added value: +{
+  "items": {},
+  "minItems": 1,
+  "type": "array"
+}
```

Changed12 schema fields changedOct 17, 2026

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"
+]

Changed14 schema fields changedOct 16, 2026

addedOutput schema / properties / active
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / daily_recap
```
Added value: +{
+  "type": "object"
+}
```
addedOutput schema / properties / day_pass
```
Added value: +{
+  "type": "object"
+}
```

addedOutput schema / properties / expires_at

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / human_line
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / intents

Added value: +{
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / next_up
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / payment
```
Added value: +{
+  "type": "object"
+}
```
addedOutput schema / properties / resume_status
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / resumed_result
```
Added value: +{
+  "type": "object"
+}
```

addedOutput schema / properties / seconds_left

Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}

addedOutput schema / properties / tier

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / today_url
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / unlock_link

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

AddedOct 16, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds substantive domain behavior beyond that: pickup status is reported separately from the client's decision/release hint, and it explicitly warns that agent pickup alone does not authorize payment release, plus the AER-1 offline-verifiable receipt claim.

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?

Three short sentences, front-loaded with the action and lookup keys, then the payment-release caveat. Every sentence carries information, though 'AER-1 receipt, verifiable offline' is terse enough to be slightly cryptic without prior context.

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 structure need not be explained, and the description still flags what the response contains (pickup status, separate decision/release hint). For a zero-required-parameter read tool with fully documented schema, this is nearly complete; only sibling routing is left implicit.

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 all eight parameters are already documented in the schema, including the distinction between handover_id and resume_code. The description's 'by ID or resume code' restates the lookup-key semantics without adding format or precedence detail beyond the schema. 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 states a specific verb and resource ('Checks a handover by ID or resume code') and names the two lookup keys. It is clearly a read-only lookup, distinct from handover_accept and handover_list, though it never names those siblings explicitly.

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?

Saying lookup can be done 'by ID or resume code' implies when the tool applies, and the optional-parameter schema makes both paths viable. However, it gives no explicit guidance on when to use this versus handover_list or handover, and no exclusions or prerequisites.

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

All Zambo tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.