Skip to main content
Glama

API Key Safety (education only)

explain_error

Read-only

Explain a common exchange API key error and how to fix it (e.g. Binance -2015, Bybit 10003/10005/10010, Bitget lost passphrase). Step-by-step pages live on quantaira.app.

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": {
      "exchange": "<exchange>",
      "code": "<code>"
    },
    "name": "explain_error"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesError code or short description, e.g. -2015, 10003, passphrase
exchangeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the notable detail that step-by-step pages live on quantaira.app, but it never clarifies whether the tool returns an explanation inline or merely links out, nor how exhaustive the answer is for unsupported exchanges.

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 action and backed by illustrative examples. The trailing 'Step-by-step pages live on quantaira.app' is slightly promotional but does carry locational information rather than pure filler.

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 simple two-parameter read-only tool with no output schema, the description should say what comes back (explanatory text, a link, or both) and note any limitations on supported errors. It hints at external pages but leaves the return shape and coverage boundaries ambiguous.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50% with the 'code' parameter documented; the 'exchange' enum has no description. The description compensates somewhat by showing how codes map to exchanges and that 'code' can be a short phrase like 'passphrase', but it gives no guidance for the okx or coinzoom enum values, leaving a real gap.

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?

States a specific verb ('Explain') and resource ('exchange API key error and how to fix it'), with concrete examples (Binance -2015, Bybit 10003/10005/10010, Bitget lost passphrase) that pin down the domain. It is clearly distinguishable from siblings like get_safe_key_checklist or get_required_permissions, though it never explicitly contrasts with them.

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?

The scope (common API key errors) implies when to call it, but there is no explicit 'use this when...' clause, no exclusions, and no pointer to the sibling tools that cover other key-related questions. The examples help the agent recognize matching inputs, which is the main reason this isn't a 2.

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.