Skip to main content
Glama

Get a link to add balance

create_balance_checkout

Returns a Stripe Checkout link where the user adds prepaid balance to the connected account. Charges nothing by itself: give the link to the user to open and pay.

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": {
      "amount_usd": "<amount_usd>"
    },
    "name": "create_balance_checkout"
  }
}

Input Schema

NameRequiredDescriptionDefault
amount_usdYesUS dollars to add.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true, readOnlyHint=false and destructiveHint=false, so the safety profile is partly covered. The description adds the crucial behavioral point that no money moves at call time and the user must complete payment out-of-band, which the annotations do not convey. Link expiry and reuse behavior are not mentioned.

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 short sentences with zero filler; the outcome is front-loaded and the clarifying constraint follows immediately.

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?

For a single-parameter link-generation tool with annotations and no output schema, the definition covers what an agent needs to call it and hand the result off correctly. Minor omissions like link expiry or currency assumptions keep it short of a 5.

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% with a documented amount_usd including a $5 minimum, so the schema carries the parameter meaning. The description adds nothing about the amount beyond implying it is the balance to add, so baseline 3 applies.

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?

States a specific verb and resource: returns a Stripe Checkout link for adding prepaid balance to the connected account. The word 'balance' distinguishes it from create_plan_checkout and get_billing_portal_link without needing to open either schema.

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

Usage Guidelines4/5

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

Explicitly tells the agent what to do with the result ('give the link to the user to open and pay') and rules out an incorrect assumption ('charges nothing by itself'). It does not name alternatives or exclusions, but the usage context is clear.

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