mcp-server

Resolve symbol to canonical coin

resolve_symbol

Read-onlyIdempotent

Map an exchange-specific or ambiguous symbol to bitcompare's canonical coin id. Useful when an exchange uses a non-standard ticker.

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": {
      "symbol": "<symbol>"
    },
    "name": "resolve_symbol"
  }
}

Input Schema

Name	Required	Description	Default
`symbol`	Yes	Exchange-specific or ambiguous symbol
`context`	No	Source exchange or quote currency to disambiguate (e.g. "kraken", "binance")

Output Schema

Name	Required	Description
`name`	Yes	Coin display name
`input`	Yes	The raw symbol that was queried
`coinId`	Yes	Canonical Bitcompare coin ID
`symbol`	Yes	Canonical symbol

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 21, 2026

changedInput schema / properties / context / description

Previous value: -"Optional source/exchange context"New value: +"Source exchange or quote currency to disambiguate (e.g. \"kraken\", \"binance\")"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "coinId": {
+      "description": "Canonical Bitcompare coin ID",
+      "type": "string"
+    },
+    "input": {
+      "description": "The raw symbol that was queried",
+      "type": "string"
+    },
+    "name": {
+      "description": "Coin display name",
+      "type": "string"
+    },
+    "symbol": {
+      "description": "Canonical symbol",
+      "type": "string"
+    }
+  },
+  "required": [
+    "input",
+    "coinId",
+    "symbol",
+    "name"
+  ],
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint. Description adds the core mapping behavior but no further traits like error handling or rate limits.

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?

Single sentence with no filler, front-loads the purpose. Every word earns its place.

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?

Has output schema (mentioned). Description covers the main use case and disambiguation. Minor gap: doesn't explain what happens if symbol can't be resolved, but annotations hint at open world.

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 covers all parameters at 100%. Description restates their purpose but adds minimal new meaning beyond the schema.

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?

Clearly states it maps symbols to canonical coin IDs, with specific verb and resource. Distinguishes from sibling resolve_symbols_batch by implying individual resolution.

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?

Explicitly says 'useful when an exchange uses a non-standard ticker', providing clear usage context. Does not exclude other uses but gives strong guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All mcp-server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?