Zambo AI Tools

New session

new_session

Read-only

Starts fresh session context and returns a new session_id. Reuse that ID on subsequent calls for continuity; changing or omitting it starts clean context. Required arguments: .

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.
`_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.

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

Changed3 schema fields changedOct 10, 2026

changedInput schema / properties / _caller_label / description

Previous value: -"Optional self-reported caller label. It is recorded as a claim, not independently verified."New value: +"Optional caller label recorded as a caller-reported claim in the receipt."

changedInput schema / properties / _session_id / description

Previous value: -"Optional stable Zambo session ID used to preserve continuity across tool calls."New value: +"Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together."

addedInput schema / properties / _zambo_key

Added value: +{
+  "description": "Optional opaque Zambo access capability. Never place it in a URL or public log.",
+  "maxLength": 160,
+  "type": "string"
+}

Changed6 schema fields changedOct 10, 2026

changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +false
```
removedOutput schema / properties / instructions
```
Removed value: -{
-  "type": "string"
-}
```

addedOutput schema / properties / result

Added value: +{
+  "description": "The tool's observed JSON value or plain-text result."
+}

removedOutput schema / properties / session_id
```
Removed value: -{
-  "type": "string"
-}
```

removedOutput schema / properties / status

Removed value: -{
-  "type": "string"
-}

addedOutput schema / required
```
Added value: +[
+  "result"
+]
```

Changed2 schema fields changedOct 10, 2026

addedInput schema / properties / _caller_label

Added value: +{
+  "description": "Optional self-reported caller label. It is recorded as a claim, not independently verified.",
+  "maxLength": 80,
+  "type": "string"
+}

addedInput schema / properties / _session_id

Added value: +{
+  "description": "Optional stable Zambo session ID used to preserve continuity across tool calls.",
+  "maxLength": 64,
+  "type": "string"
+}

Changed1 schema field changedOct 2, 2026

addedInput schema / properties / _continuity_ai_label

Added value: +{
+  "description": "Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client.",
+  "maxLength": 48,
+  "type": "string"
+}

AddedSep 26, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=false and openWorld=true; the description correctly implies a non-idempotent minting operation ('returns a new session_id') with no destruction. It adds the continuity/reset semantics, which is useful, but leaves unexplained the tension between the returned session_id and the _session_id parameter, which the schema describes as a 'stable bot-job ID', a potentially confusing overlap.

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

Conciseness3/5

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

The first two sentences are front-loaded and earn their place, but the trailing 'Required arguments: .' is a broken fragment with a dangling empty list, which reads as a template artifact and wastes the reader's attention.

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?

With an output schema present, return-value detail need not be in the description, and all optional params are documented in schema. What is missing is routing guidance against the many continuity_*/handover siblings, plus the empty required-arguments clause that signals an unfinished definition.

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 six optional parameters are documented in the schema and the baseline is 3. The description adds nothing about any parameter, and its 'Required arguments: .' clause is an empty, malformed sentence that provides no information; it also fails to clarify how _session_id relates to the returned session_id.

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?

States a specific verb and resource ('Starts fresh session context') and says what it returns (a new session_id). That is enough to distinguish it from read/query siblings like continuity_get_recent, though it never names an alternative tool 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?

It gives real usage guidance for the returned ID ('Reuse that ID on subsequent calls for continuity; changing or omitting it starts clean context'), which tells the agent how to behave after the call. It never says when to call this instead of continuity_start_thread, handover, or zambo_home, so the selection decision against siblings is left implicit.

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

All Zambo AI Tools tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?