Skip to main content
Glama

Get a wallet top-up payment link

wallet_recharge_link

Creates a one-time payment link to add credit to this organisation's prepaid wallet. amount is the wallet credit in the wallet's currency, excluding tax; the link charges credit plus tax (GST in India; zero-rated abroad). Returns a URL for the person to open and pay at the payment gateway: creating the link charges nothing, and the wallet is credited only after the gateway confirms payment. With dryRun: true it returns the credit, tax and total without creating a link. Only an owner of the organisation, or of an organisation above it, may create one.

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": "<amount>"
    },
    "name": "wallet_recharge_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesWallet credit to add, excluding tax, in the wallet's currency (e.g. 1000 for ₹1,000)
dryRunNoIf true, return the quote (credit, tax, total, gateway) without creating a link

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false) by disclosing the deferred-charge model, tax treatment (GST in India, zero-rated abroad), and the authorization requirement (owner of the organisation or above). This is exactly the mutation context an agent needs.

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?

Four sentences, each earning its place, front-loaded with purpose then amount semantics, return value, dryRun behavior and permissions. No filler or repetition.

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 mutation with no output schema, the description covers payment flow, tax, authorization and the dryRun variant. Minor gaps remain: link expiry/validity, whether repeated calls create multiple links (non-idempotent), and any currency constraints.

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 both parameters, but the description adds real meaning: amount is tax-exclusive credit while the link charges credit plus tax, and dryRun returns credit, tax and total rather than a link. Marginal addition beyond schema, hence 4 rather than 5.

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?

States a specific verb and resource ('creates a one-time payment link to add credit to this organisation's prepaid wallet') with scope and single-use nature. It is unmistakably distinct from read-oriented siblings like wallet_balance or invoice_list.

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?

Gives clear operating context: creating the link charges nothing and crediting happens only after gateway confirmation, plus a named alternative path via dryRun: true for a quote. It does not explicitly name a sibling tool, but the when-to-use and when-not-to-create distinction is clear.

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.