Skip to main content
Glama

Spend Limit Status

spend_limit_status
Read-onlyIdempotent

Read this work connection's spending cap, paid charges and remaining budget. Free, no quota. Required arguments: _session_id.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "_session_id": "<_session_id>"
    },
    "name": "spend_limit_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
_refNoOptional handover referral ID from your install link.
_zambo_keyNoOptional opaque Zambo access capability. Never place it in a URL or public log.
_session_idYesOptional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together.
_caller_labelNoOptional caller label recorded as a caller-reported claim in the receipt.zambo-starter
_caller_handleNoOpaque anonymous continuity handle returned during initialize. Reuse it across MCP sessions; it is not payment authorization.
receipt_visibilityNoReceipt visibility for this call. Public is the default. Private returns a bearer link; anyone with that link can read it, so keep it secret. The raw token is not stored.public
_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
nextNo
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 / receipt_visibility
      Added value: +{
      +  "default": "public",
      +  "description": "Receipt visibility for this call. Public is the default. Private returns a bearer link; anyone with that link can read it, so keep it secret. The raw token is not stored.",
      +  "enum": [
      +    "public",
      +    "private"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "result",
      -  "ok",
      -  "human_line",
      -  "next",
      -  "ids",
      -  "urls"
      -]New value: +[
      +  "result",
      +  "ok",
      +  "human_line",
      +  "ids",
      +  "urls"
      +]
  2. Changed8 schema fields changed
    • changedOutput schema / properties / daily_recap / type
      Previous value: -"object"New value: +[
      +  "object",
      +  "null"
      +]
    • changedOutput schema / properties / error / anyOf
      Previous value: -[
      -  {
      -    "required": [
      -      "next_call"
      -    ]
      -  },
      -  {
      -    "required": [
      -      "next_url"
      -    ]
      -  }
      -]New value: +[
      +  {
      +    "properties": {
      +      "next_call": {}
      +    },
      +    "required": [
      +      "next_call"
      +    ]
      +  },
      +  {
      +    "properties": {
      +      "next_url": {}
      +    },
      +    "required": [
      +      "next_url"
      +    ]
      +  }
      +]
    • addedOutput schema / properties / graph / properties / edges
      Added value: +{
      +  "items": {
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / graph / properties / nodes
      Added value: +{
      +  "items": {
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / graph / properties / retries
      Added value: +{
      +  "properties": {
      +    "max": {
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "used": {
      +      "minimum": 0,
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "used",
      +    "max"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / graph / properties / sources
      Added value: +{
      +  "properties": {
      +    "not_checked": {
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "not_resolved": {
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "resolved": {
      +      "minimum": 0,
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "resolved",
      +    "not_resolved",
      +    "not_checked"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / graph / properties / summary
      Added value: +{
      +  "type": "string"
      +}
    • removedOutput schema / properties / next_steps / minItems
      Removed value: -1
  3. Changed1 schema field changed
    • changedOutput schema / properties / human_line / maxLength
      Previous value: -200New value: +512
  4. 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"
  5. Changed1 schema field changed
    • changedOutput schema / properties / graph / properties / aer / const
      Previous value: -"draft-zambo-aer1-25"New value: +"draft-zambo-aer1-26"
  6. Changed1 schema field changed
    • changedOutput schema / properties / graph / properties / aer / const
      Previous value: -"draft-zambo-aer1-24"New value: +"draft-zambo-aer1-25"
  7. Changed1 schema field changed
    • changedOutput schema / properties / graph / properties / aer / const
      Previous value: -"draft-zambo-aer1-23"New value: +"draft-zambo-aer1-24"
  8. Changed1 schema field changed
    • changedOutput schema / properties / graph / properties / aer / const
      Previous value: -"draft-zambo-aer1-22"New value: +"draft-zambo-aer1-23"
  9. Changed1 schema field changed
    • changedOutput schema / properties / graph / properties / aer / const
      Previous value: -"draft-zambo-aer1-21"New value: +"draft-zambo-aer1-22"
  10. Changed1 schema field changed
    • changedOutput schema / properties / graph / properties / aer / const
      Previous value: -"draft-zambo-aer1-20"New value: +"draft-zambo-aer1-21"
  11. Changed1 schema field changed
    • addedOutput schema / properties / next_steps
      Added value: +{
      +  "items": {},
      +  "minItems": 1,
      +  "type": "array"
      +}
  12. 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"
      +]
  13. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so safety is covered. The description adds genuinely new context — the call is free with no quota, and the scope is limited to 'this work connection' rather than a global budget. It says nothing about receipt handling or the meaning of the continuity parameters, which the schema covers separately.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with zero filler: the purpose is front-loaded, the cost property follows, and the input requirement closes. Nothing could be removed without losing information.

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?

An output schema exists, so return values need no explanation, and the annotations carry the safety profile. For a simple read tool, the only minor gap is that 'work connection' is never defined for an agent that may be operating across several connections.

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%, so all seven parameters are already documented, and the description only restates that _session_id is required. That reaches the baseline of 3 but adds no extra meaning about how the continuity or receipt parameters affect a read-only status call.

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?

The description gives a specific verb ('Read') and names the exact payload: spending cap, paid charges, and remaining budget for 'this work connection'. That is concrete enough to separate it from the write-side sibling spend_limit_set, though the description never names that sibling explicitly.

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?

'Free, no quota' is a useful cost signal that encourages liberal calling, and the required argument is restated. However, there is no guidance on when to prefer this over spend_limit_set, day_pass_status, or pass_status, and no exclusions or prerequisites are given.

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