mcp-server

Similar coins

similar_coins

Read-onlyIdempotent

Coins related to the given coin by category/sector similarity.

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": {
      "coinId": "<coinId>"
    },
    "name": "similar_coins"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Max related coins to return, default 10
`coinId`	Yes	Canonical coin id to find related coins for (e.g. "bitcoin")

Output Schema

Name	Required	Description	Default
`coins`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedMay 21, 2026

addedInput schema / properties / coinId / description

Added value: +"Canonical coin id to find related coins for (e.g. \"bitcoin\")"

addedInput schema / properties / limit / description

Added value: +"Max related coins to return, default 10"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "coins": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "id": {
+            "description": "Canonical coin ID (e.g. `bitcoin`)",
+            "type": "string"
+          },
+          "marketCap": {
+            "description": "Market cap in USD",
+            "type": "number"
+          },
+          "name": {
+            "description": "Human-readable name (e.g. `Bitcoin`)",
+            "type": "string"
+          },
+          "price": {
+            "description": "Current spot price in USD",
+            "type": "number"
+          },
+          "rank": {
+            "description": "Market cap rank (1 = largest)",
+            "type": "integer"
+          },
+          "symbol": {
+            "description": "Trading symbol (e.g. `btc`)",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "symbol",
+          "name"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "coins"
+  ],
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive; description adds that similarity is based on category/sector, which provides extra behavioral context but no details on auth, rate limits, or side effects.

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, no filler, front-loaded with key 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?

Given the tool's simplicity (2 params, output schema exists), the description sufficiently explains the similarity criterion. Minor gap: no mention of default limit (10) beyond schema.

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 100% with descriptions for both parameters; description does not add meaning beyond what schema already provides, so baseline score is appropriate.

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?

Description uses specific verb 'find related coins' and resource 'coins by similarity', clearly distinguishing from siblings like 'get_coin' (single coin) or 'list_coins' (all coins).

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?

Description implies use for finding similar coins but does not specify when to use this tool versus alternatives like 'top_coins' or 'coin_history', nor provides exclusions.

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?