Zambo

Day Pass status

day_pass_status

Read-onlyIdempotent

Check a Day Pass using _zambo_key, X-Zambo-Key, or the same _session_id used at card checkout or x402 payment. Returns active, expires_at, and calls_left without spending quota. Gateway calls are unmetered while active; product/provider limits may still apply. Never returns the key.

Input Schema

TableJSON Schema

Name	Required	Description
`_zambo_key`	No	Optional opaque Zambo access capability. Never place it in a URL or public log.
`session_id`	No	Alias for _session_id.
`_session_id`	No	Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together.
`status_token`	No	Opaque token returned with the human checkout link; it is not the Day Pass key.
`_caller_label`	No	Optional caller label recorded as a caller-reported claim in the receipt.
`_continuity_ai_label`	No	Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 14, 2026

addedOutput schema / properties / result / additionalProperties
```
Added value: +true
```

removedOutput schema / properties / result / description

Removed value: -"The tool's observed JSON value or plain-text result."

addedOutput schema / properties / result / properties

Added value: +{
+  "active": {
+    "type": "boolean"
+  },
+  "calls_left": {
+    "oneOf": [
+      {
+        "minimum": 0,
+        "type": "integer"
+      },
+      {
+        "type": "string"
+      }
+    ]
+  },
+  "calls_left_scope": {
+    "type": "string"
+  },
+  "expires_at": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "seals": {
+    "items": {
+      "additionalProperties": false,
+      "properties": {
+        "sealed_at": {
+          "type": "string"
+        },
+        "workflow_id": {
+          "type": "string"
+        },
+        "workflow_url": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "workflow_id",
+        "workflow_url",
+        "sealed_at"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "session_bound": {
+    "type": "boolean"
+  },
+  "status": {
+    "type": "string"
+  }
+}

addedOutput schema / properties / result / required

Added value: +[
+  "status",
+  "active",
+  "expires_at",
+  "calls_left",
+  "seals"
+]

addedOutput schema / properties / result / type
```
Added value: +"object"
```

Changed4 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."

changedInput schema / properties / _zambo_key / description

Previous value: -"Optional Day Pass capability key. Never include it in a URL or public log."New value: +"Optional opaque Zambo access capability. Never place it in a URL or public log."

addedInput schema / properties / _zambo_key / maxLength
```
Added value: +160
```

Changed9 schema fields changedOct 10, 2026

changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +false
```

removedOutput schema / properties / active

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

removedOutput schema / properties / calls_left

Removed value: -{
-  "oneOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "number"
-    }
-  ]
-}

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

removedOutput schema / properties / expires_at

Removed value: -{
-  "oneOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}

addedOutput schema / properties / result

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

removedOutput schema / properties / session_bound
```
Removed value: -{
-  "type": "boolean"
-}
```

removedOutput schema / properties / status

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

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

AddedOct 10, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Adds real behavior beyond the annotations: it does not consume quota, gateway calls are unmetered while active but product/provider limits may still apply, and it never returns the key. These are meaningful operational and security traits that the readOnly/idempotent hints alone do not convey.

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?

Four tight sentences, front-loaded with the credential options and the non-quota-spending behavior. The return-field enumeration slightly duplicates the output schema but remains compact.

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?

For a six-parameter, zero-required auth-check tool with an output schema and rich annotations, the description covers the credential alternatives, quota semantics, and the key-safety guarantee. Nothing needed to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds value by explaining that the key can arrive via _zambo_key or the X-Zambo-Key header and by tying _session_id to the checkout/payment flow. It stops short of clarifying how status_token relates to the other credential inputs.

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 ('Check a Day Pass') and names the accepted credentials plus the fields returned (active, expires_at, calls_left). It is clearly distinct from siblings like day_pass_activate and day_pass_checkout_link, though it never names those siblings 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 Guidelines4/5

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

Gives concrete usage context: which identifiers are accepted (_zambo_key, X-Zambo-Key header, or the same _session_id used at checkout/x402 payment). It does not state when-not-to-use or point to alternatives such as day_pass_activate or day_pass_checkout_link.

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.

Resources

Need Help?