Skip to main content
Glama

Whizbrew

Get a card link

add_money

Makes a hosted card checkout link for your human to add credit; give them the link, never pay it yourself. With payment_id instead of amount_usd it says how that payment stands (poll every 5 seconds until paid). Making a link is free.

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

Input Schema

NameRequiredDescriptionDefault
amount_usdNoHow much to add, in US dollars
payment_idNoA payment made before: answer its status instead of making a link

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 declare readOnlyHint=false with destructiveHint=false, so the agent knows a non-destructive write occurs. The description adds context the annotations cannot: link creation is free, the human must complete payment rather than the agent, and status checks should be polled every 5 seconds. It does not say whether links expire or what the response payload looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is short and front-loaded with the primary action before the alternate payment_id mode. Every sentence carries information about cost, human handoff, or polling, though the alternating between modes in one paragraph makes it slightly less scannable than it could be.

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 two-parameter, zero-required-parameter tool with no output schema, the description covers both operating modes, the human-in-the-loop requirement, cost, and polling cadence. Remaining gaps such as link expiry or the shape of the status response are minor given the absence of an output schema.

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, but the description adds the mutual-exclusivity rule that payment_id is supplied instead of amount_usd, and it clarifies the resulting behavior change from creating a link to answering a status query. That is genuine meaning beyond the per-property schema text.

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 states a specific verb and resource: it creates a hosted card checkout link so a human can add credit, and it notes the alternate mode where supplying payment_id returns that payment's status. The dual-mode framing is clear, but it slightly muddies the single purpose of the tool, and it never names which sibling (e.g. get_balance or get_quote) to prefer for related tasks.

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?

Explicit usage guidance is present: give the link to the human and never pay it yourself, and poll every 5 seconds until paid when checking a payment. What is missing is an explicit when-not-to-use statement naming the alternatives, so the agent must infer that this tool is not for balance checks or quotes.

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