Skip to main content
Glama

Issue Signed Bearer Receipt

tollbooth_issue_receipt

Issue a short-lived bearer receipt token against a prepaid agent wallet to authorize API charges without moving funds. Bind each receipt to a developer, audience, amount, and method.

Instructions

Issue a short-lived Rail B rcs_receipt_hs256 bearer authorization token against an existing prepaid credit balance. Does not move bank or crypto funds.

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": {
      "walletId": "<walletId>",
      "developerId": "<developerId>",
      "audience": "<audience>",
      "amountMicros": "<amountMicros>"
    },
    "name": "tollbooth_issue_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
methodNoHTTP verb constraint (e.g., GET, POST) or '*'.
schemeNoPayment authorization scheme ('exact' fixed charge or 'upto' metered ceiling).
audienceYesTarget URL path, route pattern, or '*' wildcard audience bound to the receipt.
walletIdYesSource prepaid agent wallet identifier.
developerIdYesRecipient API developer identifier registered in the clearinghouse.
amountMicrosYesMaximum debit amount in integer USD microdollars.
idempotencyKeyNoOptional idempotency key to prevent duplicate debit charges on retries.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare the safety profile (non-read-only, non-destructive, non-idempotent, closed-world); the description adds genuinely new behavior: the credential is short-lived, it authorizes against an existing prepaid balance, and no bank or crypto funds move. It still omits token expiry length, what happens to the balance on issuance versus redemption, and failure modes.

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 tightly packed sentences with zero filler; the core action and the token format come first, and the scope-limiting clause follows. Nothing is redundant or padded.

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?

With 7 parameters and no output schema, the description should say more about what the caller receives (token string? expiry field?) and how long 'short-lived' is. It is adequate for understanding the action but thin on return shape and error conditions for a mutation-with-financial-consequence tool.

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 every parameter (walletId, developerId, audience, amountMicros, method, scheme, idempotencyKey) is already documented in the schema. The description adds no meaning beyond that — it mentions neither the wallet/developer binding nor the exact/upto scheme trade-off.

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 names a specific verb and resource: issuing a short-lived 'rcs_receipt_hs256 bearer authorization token' against a prepaid credit balance. The closing clause ('Does not move bank or crypto funds') implicitly separates it from the sibling checkout/x402 tools, though no sibling is named directly.

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?

Usage is implied by the requirement of an 'existing prepaid credit balance' and by the explicit exclusion of fund movement, which points agents elsewhere for actual transfers. It never names an alternative tool (e.g. tollbooth_create_topup_checkout or tollbooth_verify_x402) or states when to prefer this versus a quote, so routing is left to inference.

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