Skip to main content
Glama

Add to the balance

add_balance

Starts a purchase of a fovub pack, which adds dollars to the user's fovub balance, and returns a link to Stripe's payment page, where the user pays in a browser. The balance rises when Stripe confirms the payment. With several packs for sale and no price_id, it lists the packs. Needs the user's fovub sign-in.

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_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
price_idNoThe pack's price_id, from the packs add_balance listed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the safety profile is largely covered. The description adds genuinely non-obvious behavior: the call only returns a payment link, the user completes payment in a browser, and the balance changes only after Stripe confirms. It does not address what happens on repeated calls, which is relevant given idempotentHint=false.

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?

Every sentence carries distinct information—effect, return value, timing of balance change, no-parameter behavior, auth prerequisite—and the core purpose is front-loaded. The prose is somewhat run-on with repeated 'fovub' phrasing, but there is no filler to cut.

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?

With no output schema, the description correctly compensates by describing the return value as a Stripe payment link. It also covers the auth requirement and the two calling modes. Missing is any note on failure cases or whether a pending purchase blocks a second call, which matters for a non-idempotent purchase tool.

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 documented there, so the baseline would be 3. The description earns above baseline by explaining the optional-parameter semantics: omitting price_id is not an error but a listing mode, which the schema does not convey on its own.

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?

The description gives a specific verb and resource ('Starts a purchase of a fovub pack') and spells out the effect ('adds dollars to the user's fovub balance') plus the return value ('a link to Stripe's payment page'). An agent can immediately distinguish this from siblings like account, check_projection, or find_seat, which share no such purchase semantics.

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 states a clear conditional call path: with no price_id it lists the packs, and with a price_id it starts the purchase. It also flags the prerequisite ('Needs the user's fovub sign-in'). It stops short of naming when NOT to use it or pointing at an alternative tool, which is the only thing separating this from a 5.

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