Zambo AI Tools

Spend Limit SET

spend_limit_set

Idempotent

Set this work connection's daily and optional monthly dollar cap before further Day Pass payments. Free, no quota. Required arguments: _session_id, daily_usd.

Input Schema

Name	Required	Description	Default
`_ref`	No	Optional handover referral ID from your install link.
`daily_usd`	Yes
`_zambo_key`	No	Optional opaque Zambo access capability. Never place it in a URL or public log.
`_session_id`	Yes	Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together.
`monthly_usd`	No
`_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

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly=false, idempotent=true, destructive=false, openWorld=true. The description adds genuinely new behavior: this acts as a gate that must be set before further Day Pass payments, and the call itself consumes no quota. It does not explain what happens to an existing cap when re-set, which keeps it out of 5 territory.

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 front-loaded sentences with no filler; the gating condition leads. The final 'Required arguments' sentence largely duplicates the schema's required array, which costs it a point.

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

Completeness5/5

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

An output schema exists and annotations cover the safety profile, so the description only needs to establish purpose, cost, and sequencing — all three are present. Nothing an agent needs to invoke this correctly is missing.

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% and the schema already documents the optional session, caller, and continuity parameters. The description repeats the required argument list from the schema and flags monthly_usd as optional, adding no semantics beyond that. Baseline 3 is appropriate.

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 verb and resource (set a daily and optional monthly dollar cap on this work connection) with a scope qualifier ('this work connection's'), which naturally separates it from the read-only sibling spend_limit_status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear triggering condition: call this before further Day Pass payments, and notes it is free with no quota. It does not name an explicit alternative or state when not to call it, but the sequencing guidance is concrete enough to act on.

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?