Skip to main content
Glama

DAY Pass Redeem

day_pass_redeem
Read-onlyIdempotent

Unlock this AI with your private Day Pass link. No headers needed. The link expires with the original pass.

Input Schema

NameRequiredDescriptionDefault
urlNoAlias for token_or_link.
_refNoOptional handover referral ID from your install link.
tokenNoAlias for token_or_link.
_zambo_keyNoOptional opaque Zambo access capability. Never place it in a URL or public log.
_session_idNoOptional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together.
unlock_linkNoAlias for token_or_link.
_caller_labelNoOptional caller label recorded as a caller-reported claim in the receipt.zambo-starter
token_or_linkNoDay Pass token or unlock URL.
_caller_handleNoOpaque anonymous continuity handle returned during initialize. Reuse it across MCP sessions; it is not payment authorization.
_continuity_ai_labelNoOptional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client.

Output Schema

NameRequiredDescriptionDefault
okYes
idsYes
nextYes
tierNo
urlsYes
errorNo
graphNo
activeNo
resultYesThe tool's observed JSON value or plain-text result.
intentsNo
next_upNo
paymentNo
day_passNo
today_urlNo
expires_atNo
human_lineYes
next_stepsNo
daily_recapNo
renew_nudgeNo
unlock_linkNo
seconds_leftNo
resume_statusNo
resumed_resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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"
  2. Changed1 schema field changed
    • changedOutput schema / properties / graph / properties / aer / const
      Previous value: -"draft-zambo-aer1-25"New value: +"draft-zambo-aer1-26"
  3. Changed1 schema field changed
    • changedOutput schema / properties / graph / properties / aer / const
      Previous value: -"draft-zambo-aer1-24"New value: +"draft-zambo-aer1-25"
  4. Changed1 schema field changed
    • changedOutput schema / properties / graph / properties / aer / const
      Previous value: -"draft-zambo-aer1-23"New value: +"draft-zambo-aer1-24"
  5. Changed1 schema field changed
    • changedOutput schema / properties / graph / properties / aer / const
      Previous value: -"draft-zambo-aer1-22"New value: +"draft-zambo-aer1-23"
  6. Changed1 schema field changed
    • changedOutput schema / properties / graph / properties / aer / const
      Previous value: -"draft-zambo-aer1-21"New value: +"draft-zambo-aer1-22"
  7. Changed1 schema field changed
    • changedOutput schema / properties / graph / properties / aer / const
      Previous value: -"draft-zambo-aer1-20"New value: +"draft-zambo-aer1-21"
  8. Changed1 schema field changed
    • addedOutput schema / properties / next_steps
      Added value: +{
      +  "items": {},
      +  "minItems": 1,
      +  "type": "array"
      +}
  9. Changed12 schema fields changed
    • 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"
      +]
  10. Changed7 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +true
    • addedInput schema / anyOf
      Added value: +[
      +  {
      +    "required": [
      +      "token_or_link"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "token"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "unlock_link"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "url"
      +    ]
      +  }
      +]
    • addedInput schema / properties / token
      Added value: +{
      +  "description": "Alias for token_or_link.",
      +  "type": "string"
      +}
    • addedInput schema / properties / token_or_link / description
      Added value: +"Day Pass token or unlock URL."
    • addedInput schema / properties / unlock_link
      Added value: +{
      +  "description": "Alias for token_or_link.",
      +  "type": "string"
      +}
    • addedInput schema / properties / url
      Added value: +{
      +  "description": "Alias for token_or_link.",
      +  "type": "string"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "token_or_link"
      -]
  11. Added

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false. The description adds two genuinely useful facts beyond that: no headers/auth plumbing are required, and the link expires with the original pass. It still doesn't say what redemption returns or what happens on an expired or already-redeemed link, which matters for a call whose name implies a state change.

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 declarative sentences with no filler, and the core action is front-loaded. It is arguably too terse for the tool's complexity, but nothing is wasted.

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 the schema documents all 10 parameters. What's missing is the operational context: the relationship to day_pass_activate/day_pass_status, and the failure/expiry behavior of redemption, which is the main risk an agent needs to know.

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% and every parameter (token, url, unlock_link, token_or_link, _session_id, _zambo_key, etc.) carries its own description, so the schema does the work. The description only gestures at 'your private Day Pass link' and adds no alias or precedence guidance (e.g., that token/url/unlock_link are all aliases of token_or_link).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the verb 'unlock' (redeem) and the resource 'Day Pass link', so the general intent is graspable. But it never distinguishes redemption from the sibling tools day_pass_activate, day_pass_status, and day_pass_checkout_link, so an agent cannot tell from the text which one actually grants access versus activates or checks.

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

Usage Guidelines2/5

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

'Unlock this AI with your private Day Pass link' implies a precondition (you have a private link) but gives no explicit when-to-use / when-not-to-use rules and never names the alternatives it competes with. An agent arriving with a token but no guidance on activate-vs-redeem is left to guess.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources