Skip to main content
Glama

Get top-up link

topup_link
Read-onlyIdempotent

Returns the page where the prepaid balance can be topped up, plus the minimum amount.

Use when: the balance is empty or too low for the documents the user wants to process. Do not use when: the balance is sufficient — check it with get_balance first.

Side effects and cost: none. The call only builds a link; the payment happens in the browser and is handled by the payment provider, never by this server.

Parameter interactions and edge cases: amount_eur is echoed back only; a value outside 8..5000 is rejected by parameter validation before the call runs. The returned url is a pricing page, not a payment link tied to a sum — the user chooses the amount there. Calling it repeatedly returns the same page and creates no orders.

Returns: {ok, url, minimum_eur}.

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

Input Schema

NameRequiredDescriptionDefault
amount_eurNoPlanned top-up in euro, minimum 8, maximum 5000, default 8. Informational only: it does not create an order or reserve money, it is echoed back in requested_eur so the assistant can show the user what was intended.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / amount_eur / description
      Added value: +"Planned top-up in euro, minimum 8, maximum 5000, default 8. Informational only: it does not create an order or reserve money, it is echoed back in requested_eur so the assistant can show the user what was intended."
    • addedInput schema / properties / amount_eur / maximum
      Added value: +5000
    • addedInput schema / properties / amount_eur / minimum
      Added value: +8
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description goes well beyond them: it states no payment occurs on the server, the URL is a generic pricing page rather than a link bound to a sum, repeated calls create no orders, and no money is reserved. It also discloses that out-of-range input is rejected by validation before execution.

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?

Labeled sections (when to use, when not to use, side effects, parameters, returns) make it skimmable and the guidance is front-loaded. Slightly redundant in restating amount_eur's 'informational only' nature twice and the echo field inconsistently.

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?

There is no output schema, so the description correctly supplies the return shape {ok, url, minimum_eur}. For a single optional parameter with full schema coverage, the definition covers safety, cost, idempotency, and error behavior, leaving nothing an agent needs missing.

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 already documents amount_eur's bounds and default, yet the description adds real meaning: the value is informational only, creates no order, and is echoed back. Minor deduction because the description says the amount is echoed in 'requested_eur' while its own Returns line lists only {ok, url, minimum_eur}, leaving a small internal inconsistency.

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 first sentence names a specific verb (returns) and a specific resource (the page where prepaid balance can be topped up) plus an accompanying datum (minimum amount). An agent can distinguish this from get_balance, get_result, and parse_invoice without opening any schema.

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

Usage Guidelines5/5

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

Provides explicit when-to-use ('balance is empty or too low for the documents the user wants to process'), explicit when-not-to-use ('balance is sufficient'), and names the alternative tool (get_balance) that determines the condition. No sibling inference is required.

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.