Skip to main content
Glama

Top up wallet

spur_top_up_wallet

Creates a Stripe checkout link to add funds to the user's Spur wallet (pays for postcards, letters, SMS, data credit and action top-ups, and other usage beyond the plan). No money moves until the user pays on Stripe, so no confirmation is needed. If the user didn't name an amount, suggest $25, $50 or $100, or enough to cover the send they're planning.

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

Input Schema

NameRequiredDescriptionDefault
amount_usdYesAmount to add in US dollars (minimum $5)

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 establish that this is a non-read-only, open-world, non-destructive operation, and the description adds meaningful behavior beyond that: it is a deferred-payment link, money only moves on Stripe, and no confirmation is required. That resolves the main ambiguity for an agent about whether calling it is consequential. It leaves the non-idempotent trait (repeated calls create multiple checkout links) and any auth/permission requirements unstated.

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 sentences, each doing distinct work: what the tool creates and why, what the payment behavior means for confirmation, and how to pick an amount when the user was vague. The key non-obvious fact (no confirmation needed) is front-loaded right after the purpose, with no filler or repetition of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter tool with no output schema, this covers the essentials: what it produces (a Stripe checkout link), when calling it is safe, and how to choose the amount. The only untouched details are the non-idempotency of repeat calls and where the link is returned, which is a small gap given the otherwise specific description.

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% and the single parameter is already documented with its type and minimum $5, so the schema carries the baseline. The description still adds genuine meaning the schema cannot: fallback amounts of $25, $50 or $100 and the 'enough to cover the send they're planning' heuristic for choosing a value. The $10,000 maximum is not echoed, but that is minor.

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 specific verb and resource: it 'Creates a Stripe checkout link to add funds to the user's Spur wallet', and it enumerates what the wallet pays for (postcards, letters, SMS, data credit, action top-ups). That is far more concrete than the title 'Top up wallet'. It does not, however, name or contrast a sibling such as spur_buy_credit_pack or spur_change_plan, so the agent must infer the boundary between funding the wallet and buying a credit pack.

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?

The definition gives a clear usage rule: 'No money moves until the user pays on Stripe, so no confirmation is needed', which directly tells the agent it can call this without asking permission first. It also instructs on what to propose when the user gave no amount ($25/$50/$100 or enough to cover the planned send). It stops short of explicit when-not / use-alternative-instead guidance against neighboring purchase tools.

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