Zambo AI Tools

Memory Remember

memory_remember

Save a private fact for this work connection. Respects Memory capture settings. Free, no quota. Required arguments: _session_id, fact.

Input Schema

Name	Required	Description	Default
`_ref`	No	Optional handover referral ID from your install link.
`fact`	Yes
`_zambo_key`	No	Optional opaque Zambo access capability. Never place it in a URL or public log.
`agent_name`	No
`_session_id`	Yes	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"
+]

AddedOct 16, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true). The description adds genuinely new context: facts are private per work connection, capture settings may affect saving, and calls are free with no quota. It omits duplicate-handling behavior despite idempotentHint=false, which an agent would want to know.

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 core action and scoping constraint. The 'Required arguments' sentence largely duplicates the schema's required list but is brief enough not to be costly.

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?

An output schema exists, so return values need no explanation, and annotations cover mutability. However, with 8 parameters the description never explains the optional fields or how saved facts surface later via memory_recall, leaving an agent to infer the write/read lifecycle.

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 75%, so the schema already documents most parameters. The description only restates that _session_id and fact are required — information already in the required array — and adds nothing about what counts as a valid fact (500-char cap) or the role of optional fields like agent_name. 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?

States a concrete verb and resource ('Save a private fact') plus the scope ('for this work connection'), which is more specific than the bare name. It does not explicitly name memory_recall as the retrieval counterpart, so sibling differentiation is left to inference from naming.

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?

'Respects Memory capture settings' hints at preconditions, but there is no explicit statement of when to use this versus memory_recall, when not to use it, or what capture settings actually gate. Usage is implied by the remember/recall pairing rather than stated.

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?