Skip to main content
Glama

Crypto Support Desk (zh/en)

How to unlock the full kit (free)

payment_options
Read-onlyIdempotent

FREE. Price ($5.00), receiving addresses and the exact USDC/USDT contracts accepted on each chain, and how to redeem with pay_tx. Plain transfer from any wallet or exchange withdrawal; no x402 client and no account needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed-world scope, so the safety profile is fully covered structurally. The description adds genuinely useful operational context beyond that: payment is a plain wallet transfer or exchange withdrawal, no x402 client and no account is required. It does not, however, describe the shape or ordering of the returned payment options, and with no output schema the description carries that burden alone.

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?

Two short sentences, front-loaded with the 'FREE' qualifier and the concrete data points an agent needs. The phrase 'How to unlock the full kit' in the title is promotional rather than informative, but the description body itself is tight and wastes little space.

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

Completeness3/5

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

For a zero-parameter, no-output-schema informational tool, the description covers what is returned and how the payment is executed, which is most of what an agent needs. It stops short of saying whether results are grouped per chain or what happens after payment is sent, leaving the agent to infer the follow-up step into pay_tx.

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?

The tool takes zero parameters, so the baseline is 4; the description correctly implies no input is needed to obtain the pricing and address list. Nothing in the schema requires further explanation.

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 enumerates what the tool surfaces: price ($5.00), receiving addresses, the exact USDC/USDT contracts accepted per chain, and redemption steps. That is a concrete resource statement an agent can act on, though it names no verb and does not explicitly distinguish itself from the sibling support/lookup tools (which are obviously unrelated, so the risk is low).

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

Usage Guidelines3/5

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

Usage is only implied through the mention of redeeming 'with pay_tx', which signals a sequencing relationship (fetch payment details before calling pay_tx). There is no explicit when-to-use statement, no exclusions, and no guidance about when the address-checking or support siblings would be preferable.

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