Skip to main content
Glama

Crypto Support Desk (zh/en)

Get a bilingual support reply (free 01/04/11/12/22; others $5.00 once)

get_support_reply
Read-onlyIdempotent

Returns the ready-to-send reply for one scenario: what to ask the user first, the reply in Chinese and in English, and an internal note for the agent. Scenarios 01, 04, 11, 12, 22 are FREE. Others return a preview plus payment instructions until you pass pay_tx: one plain transfer of >= $5.00 USDC/USDT (Base, Arbitrum, OP, Polygon, BSC, Ethereum or Solana; not x402) unlocks all scenarios, and scenario="all" returns the whole kit.

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": {
      "scenario": "<scenario>"
    },
    "name": "get_support_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
pay_txNoOnly for paid scenarios: hash of ONE transfer of >= $5.00 USDC/USDT to the store address (see payment_options). EVM: 0x + 64 hex; Solana: signature.
scenarioYesScenario id "01".."25", or "all" for the whole kit, or a few words describing the problem (the best match is used)
pay_chainNoChain of pay_tx. Default base (a base58 signature means solana).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses the gating behavior that matters most: paid scenarios degrade to a preview rather than failing, one plain transfer unlocks all scenarios, and x402 is explicitly excluded. The accepted chains and the USDC/USDT threshold are stated, so the agent understands the full pay-then-retry flow.

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?

Three sentences ordered by importance—what is returned, what is free, how payment unlocks the rest—with no filler. The parenthetical chain list is dense but earns its place by removing a follow-up question about accepted networks.

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 carries the burden of describing returns, and it does: ask-first prompt, bilingual reply, internal note, preview-plus-instructions when unpaid. Payment mechanics are complete enough to act on, with payment_options named as the source of the store address.

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?

With 100% schema coverage the baseline is 3, but the description adds meaning the schema does not: pay_tx is scoped to ONE transfer that unlocks all scenarios, not just the requested one, and the payment must not be x402. It also clarifies the free-text matching behavior of scenario beyond the schema's id/all/words enumeration.

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 (returns the ready-to-send reply for one scenario) and enumerates the payload: what to ask the user first, the Chinese and English reply, and an internal agent note. The scenario="all" variant is also spelled out, so an agent knows exactly what it gets.

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 operational context: scenarios 01, 04, 11, 12, 22 are free, everything else returns a preview plus payment instructions until pay_tx is supplied, and scenario="all" fetches the whole kit. It does not explicitly route to siblings such as list_support_scenarios for discovering IDs, but the fuzzy-match fallback ("a few words describing the problem") makes the tool usable without them.

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