Skip to main content
Glama

Crypto Support Desk (zh/en)

Search crypto support scenarios (free)

search_support_scenarios
Read-onlyIdempotent

FREE. Find the right support scenario for a user's problem, in English or Chinese (e.g. "sent USDT on the wrong network", "忘填memo", "fake support DM", "seed phrase leaked"). Returns up to 5 scenario ids with titles and whether each is free.

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": {
      "query": "<query>"
    },
    "name": "search_support_scenarios"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesThe user's problem in a few words (English or Chinese)

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 readOnly, idempotent, closed-world, non-destructive behavior, so the safety profile is covered. The description still adds real value beyond them: it flags the tool as FREE and discloses the result cap (up to 5) and the per-result fields (id, title, free flag). Only pagination/truncation behavior when more than 5 match is left unstated.

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?

Two sentences with no filler; the FREE marker and the core purpose are front-loaded, followed by examples and return shape. Every clause carries information an agent would act on.

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?

For a single-parameter, read-only lookup with no output schema, the description covers purpose, language handling, input style, cost, and return contents. Nothing an agent needs to call it correctly is 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 there is only one parameter, so the schema already defines it. The description nonetheless adds semantic guidance the schema lacks: the query may be English or Chinese and should be a short problem phrase, illustrated with four realistic example queries including a Chinese one.

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?

Specific verb+resource ('Find the right support scenario') with concrete example queries in both English and Chinese, and it states the return shape (up to 5 scenario ids with titles). An agent can distinguish this from a plain listing tool like list_support_scenarios based on the 'find the right one for a user's problem' framing.

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 implied by 'for a user's problem' and the sample queries, which give a clear sense of the input granularity. However, there is no explicit when-to-use vs. when-not, and no sibling (e.g. list_support_scenarios or get_support_reply) is named as an alternative path.

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