Skip to main content
Glama

Get Budget Remaining

paybond_get_budget_remaining
Read-only

Check remaining budget for a tenant-bound intent before authorizing a paid tool. Use this read-only dry-run to avoid overspending.

Instructions

Use this when you need a read-only dry-run of remaining spend budget for a tenant-bound intent before authorizing a paid tool. Do not use this to authorize spend or create decisions; call paybond_authorize_agent_spend when you are ready to gate a side-effecting tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idNoOptional task scope hint for policy evaluation.
currencyNoOptional ISO currency code for the proposed spend.
intent_idYesCanonical Harbor intent UUID.
operationNoOptional delegated operation or tool name. Defaults to * when omitted.
tool_nameNoOptional tool name scope hint for policy evaluation.
vendor_idNoOptional vendor scope hint for policy evaluation.
workflow_idNoOptional workflow scope hint for policy evaluation.
tool_call_idNoOptional tool-call correlation id for policy evaluation.
agent_subjectNoOptional agent subject for agent-scoped caps.
approval_tokenNoOptional approval token to evaluate against pending approval state (not consumed).
requested_spend_centsNoOptional proposed spend in cents for the dry-run evaluation.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
spend_scopeNoSpend scope used for the budget evaluation (scope_type and scope_key).
policy_versionNoActive spend-control policy version when a policy is configured.
remaining_centsNoRemaining spend budget in cents for the evaluated scope, when available.
Behavior4/5

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

Annotations declare readOnlyHint=true; description adds that it's a dry-run and not authorizing spend, reinforcing the read-only nature and policy-evaluation context.

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?

Two sentences, front-loaded with purpose and usage guidance, no redundancy.

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?

Given the output schema exists and the tool has 11 parameters (only 1 required), the description covers the core purpose and usage well, though it doesn't detail output structure (covered by output schema).

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 100%, so baseline is 3. Description does not add parameter-specific meaning beyond schema, but the parameters are self-explanatory given the dry-run context.

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?

The description clearly states the tool performs a 'read-only dry-run of remaining spend budget' for a specific resource (tenant-bound intent) and distinguishes it from authorization tools.

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

Usage Guidelines5/5

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

Explicitly states when to use ('before authorizing a paid tool') and when not to use, directing to the sibling tool paybond_authorize_agent_spend.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nonameuserd/paybond-kit'

If you have feedback or need assistance with the MCP directory API, please join our Discord server