Skip to main content
Glama

Add balance by charging the saved card

charge_saved_card
Destructive

Charges the connected account's saved card and adds the amount to its balance. This spends the user's money at once. It only works if the user allowed card charges when connecting, up to their daily limit (see get_account). Use it when the user asked you to, or told you to keep the balance funded.

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": "charge_saved_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
amount_usdYesUS dollars to charge.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag destructive=true, idempotent=false and openWorld=true, so the description earns credit for adding the authorization requirement and daily-limit precondition that annotations cannot express. It also warns that funds are spent immediately, which is the key irreversibility cue. It does not explain failure behavior, partial outcomes, or whether a retry could double-charge.

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?

Three tight sentences: what it does, its risk profile, then its eligibility constraints and usage trigger, with a pointer to get_account for limit lookup. No filler and the riskiest information is front-loaded.

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 destructive single-parameter mutation with no output schema, the description covers the essentials an agent needs before calling: money leaves the account, permission is required, and a daily ceiling applies. Residual gaps are behavioral detail (failure modes, resulting balance in the response) rather than decision-critical facts.

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% and the single parameter carries its own description plus a minimum of 5, so the schema does the heavy lifting. The description adds nothing about amount semantics — no mention of the minimum, currency handling, or how the amount interacts with the daily limit.

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 uses a concrete verb and resource ("Charges the connected account's saved card") and states the effect ("adds the amount to its balance"), so the agent knows exactly what happens. It implies a distinction from checkout-style siblings via "spends the user's money at once," but never names an alternative such as create_balance_checkout, so the differentiation is indirect.

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?

It gives a positive usage context ("when the user asked you to, or told you to keep the balance funded") plus a hard precondition — card charges must have been enabled at connect time and are bounded by a daily limit. It stops short of stating when not to use it or which sibling to prefer for a user-initiated top-up flow.

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