Zambo

DAY Pass Checkout Link

day_pass_checkout_link

Idempotent

Get a checkout link for the $0.99, 24-hour Day Pass by card or PayPal, including in a fresh session. Creating the link never charges anyone; payment requires completing checkout. Optional workflow_id targets a closed run; sponsor:true explicitly sponsors another team's run without transferring branding ownership. AER-1 receipt, verifiable offline. Required arguments: .

Input Schema

Name	Required	Description	Default
`_ref`	No	Optional handover referral ID from your install link.
`sponsor`	No	Explicitly sponsor a closed workflow owned by another session; this never grants branding access.
`_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.
`workflow_id`	No	Optional closed workflow to save with proof after payment.
`_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.
`human_approved`	No	Optional confirmation that the person requested a link. Creating a link never charges them.
`_continuity_ai_label`	No	Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client.
`workflow_manage_token`	No	Optional private workflow capability. Never share it in public.

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 1, 2026

changedInput schema / properties / workflow_id / description

Previous value: -"Optional closed workflow to seal after payment."New value: +"Optional closed workflow to save with proof after payment."

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

Changed3 schema fields changedOct 17, 2026

changedInput schema / properties / human_approved / description

Previous value: -"Must be true only after the human explicitly agrees to receive a checkout link."New value: +"Optional confirmation that the person requested a link. Creating a link never charges them."

changedInput schema / required

Previous value: -[
-  "human_approved"
-]New value: +[]

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 14, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations only say readOnlyHint=false, idempotentHint=true and destructiveHint=false; the description adds substantive context beyond that — link creation is non-charging, the sponsor flag never transfers branding ownership, and an offline-verifiable AER-1 receipt is issued. It does not cover rate limits or what the returned link's lifetime is, which keeps it short of a 5.

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 core content is front-loaded and dense, but the definition ends with a dangling fragment, 'Required arguments: .', which is leftover template noise implying required parameters that do not exist (required=[]). That artifact works against the otherwise efficient single-paragraph structure.

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 values need no explanation, and annotations cover the safety profile; the description supplies the pricing, payment, sponsorship and receipt facts an agent needs to call it correctly. Only the sibling-routing guidance and link expiry behavior are 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 description coverage is 100% across 11 parameters, so the schema already explains _ref, _zambo_key, _caller_handle, human_approved and the rest. The description adds only meaning for workflow_id and sponsor, which the schema also documents, so per the baseline rule a 3 is appropriate.

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?

Specific verb and resource: it produces a checkout link for the $0.99 24-hour Day Pass, with payment-channel and fresh-session scope stated. It is clearly a different action from the sibling redeem/activate/status tools, though it never names them 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?

The description implies the correct point in the flow ('Creating the link never charges anyone; payment requires completing checkout') and scopes the two conditional arguments (workflow_id for a closed run, sponsor for another team's run). It never states when to call this instead of day_pass_activate or day_pass_redeem, so the agent must infer the ordering.

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.