Skip to main content
Glama

Authorize Agent Spend

paybond_authorize_agent_spend

Authorizes a tenant-bound spend gate for an agent using an intent ID and capability token, enabling secure payment for side-effecting tool calls or vendor actions.

Instructions

Use this when an agent has an intent_id and capability_token and needs a tenant-bound spend gate before calling a side-effecting tool, paid API, vendor action, or settlement workflow. Do not use this for creating, funding, or changing intents; call paybond_create_spend_intent or paybond_fund_intent first when no funded capability token exists.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenNo
intent_idYes
operationYes
requested_spend_centsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
allowNoWhether the requested operation is allowed.
tenantYesTenant echoed by the gateway.
messageNoHuman-readable decision message when present.
audit_idNoGateway audit identifier when available.
intent_idYesVerified Harbor intent UUID.
decision_idNoPersisted spend decision identifier when authorization creates one.
reason_codesNoStable spend-policy reason codes from the authorization decision.
remaining_centsNoRemaining spend budget in cents for the evaluated scope, when available.
approval_request_idNoApproval request identifier when human approval is required.
Behavior3/5

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

Annotations indicate a mutating but non-destructive operation. Description adds context about 'tenant-bound spend gate' but lacks details on side effects, reversibility, or budget impact.

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 primary purpose and negative guidance, no wasted words.

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?

Despite existence of output schema, missing explanation of what authorization returns and the meaning of parameters like 'operation' and 'requested_spend_cents'.

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

Parameters2/5

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

With 0% schema coverage, description only mentions intent_id and capability_token (as 'token') but fails to explain 'operation' or 'requested_spend_cents', leaving key parameters ambiguous.

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 it authorizes agent spend for side-effecting actions, distinguishing from siblings like paybond_create_spend_intent for creating intents.

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 says when to use (agent has intent_id and capability_token) and when not to (creating or funding intents), directing to specific alternative tools.

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-python'

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