Skip to main content
Glama

Agent Tollbooth 402

Generate Checkout Link URL

tollbooth_create_topup_checkout
Read-onlyIdempotent

Return a Stripe Checkout or sandbox link URL that a user can open in a browser to fund a wallet ($1+) or purchase a Pro ($39) / Agency ($79) Pass. Never charges automatically.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tollbooth_create_topup_checkout"
  }
}

Input Schema

NameRequiredDescriptionDefault
passTierNoOne-time developer tier upgrade to unlock 3% clearinghouse fee.
walletIdNoAgent wallet identifier to top up via Stripe Checkout.
amountUsdNoTop-up amount in USD (minimum $1).
developerIdNoDeveloper identifier for Pro ($39) or Agency ($79) pass upgrades.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: the output is a link the user opens manually, and "Never charges automatically" preempts the obvious fear that calling this tool takes money. What's missing is link lifetime/expiry and how sandbox vs. live mode is selected.

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?

A single dense sentence that front-loads the return value and follows with the two supported flows and a safety reassurance. No filler, no restatement of the title, nothing to cut.

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 zero required parameters and no output schema, the critical missing piece is the two mutually-exclusive calling modes: top-up needs walletId + amountUsd, upgrade needs developerId + passTier. The description lists the flows but never states that requirement, leaving an agent to guess which fields to send together.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns extra credit by supplying pricing that the schema omits ($1 minimum for top-ups, $39 Pro, $79 Agency) and by pairing amounts with wallet top-up versus tiers with passes. It still does not clarify that walletId/amountUsd and developerId/passTier are alternative modes.

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?

Names a specific verb and artifact ("Return a Stripe Checkout or sandbox link URL") plus the two supported purposes: wallet funding and pass purchase, with concrete price points ($1+, $39, $79). An agent immediately knows this produces a payment link rather than moving money. It does not name or route away from any sibling, so it stops short of 5.

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 through the stated outcome ("a user can open in a browser to fund a wallet ... or purchase a ... Pass"), which is enough to infer the trigger condition. There is no explicit when-not guidance, no mention of when to prefer tollbooth_pricing_quote or tollbooth_wallet_balance first, and no stated prerequisites.

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