Skip to main content
Glama

whale-data

by com.coinlobster
OverviewDiscussionsAdmin

Find a coin

coin_search
Read-onlyIdempotent

Find a coin by symbol or name and learn the symbol the other tools take, whether it is covered and whether it is free, with price and 24h change. Free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coinNoCoin symbol, e.g. BTC. A pair like ETH/USD works too.
limitNoRows to return (usually up to 20; more is clamped and said).
queryNoSymbol or part of a name, e.g. "sol".
cursorNoNext page: the cursor from the previous answer.
detailNobrief (default): the answer, key numbers and top rows. full: every row, paged with cursor.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
as_ofNoData time, ISO.
caveatNoA real limit, when non-null.
cursorNoNext page (detail full).
delayedNoSet when not live.
summaryNoThe answer in one sentence.
as_of_msNoData time, Unix ms.
availableNoFalse: no data; note says why.
truncatedNoRows held back; see trimmed.
next_toolsNoFollow-up calls {tool,args,why}.
access_noteNoWhat this connection could not return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed27 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +{}
    • changedInput schema / properties / coin / description
      Previous value: -"Alias for query."New value: +"Coin symbol, e.g. BTC. A pair like ETH/USD works too."
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Next page: the cursor from the previous answer.",
+  "type": "string"
+}
    • addedInput schema / properties / detail
      Added value: +{
+  "description": "brief (default): the answer, key numbers and top rows. full: every row, paged with cursor.",
+  "enum": [
+    "brief",
+    "full"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / limit / description
      Previous value: -"Max matches. Defaults to 10, hard ceiling 20 for everyone."New value: +"Rows to return (usually up to 20; more is clamped and said)."
    • removedInput schema / properties / limit / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / limit / minimum
      Removed value: --9007199254740991
    • removedInput schema / properties / pair
      Removed value: -{
-  "description": "Alias for query (a pair like SOL/USD searches its base).",
-  "type": "string"
-}
    • changedInput schema / properties / query / description
      Previous value: -"Symbol or part of a name, for example \"sol\" or \"pepe\"."New value: +"Symbol or part of a name, e.g. \"sol\"."
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedOutput schema / properties / access_note
      Added value: +{
+  "description": "What this connection could not return."
+}
    • addedOutput schema / properties / as_of
      Added value: +{
+  "description": "Data time, ISO."
+}
    • addedOutput schema / properties / as_of_ms
      Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Data time, Unix ms."
+}
    • removedOutput schema / properties / available / anyOf
      Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
    • changedOutput schema / properties / available / description
      Previous value: -"False when nothing was searched (no query) or the catalog has not loaded."New value: +"False: no data; note says why."
    • addedOutput schema / properties / available / type
      Added value: +"boolean"
    • addedOutput schema / properties / caveat
      Added value: +{
+  "description": "A real limit, when non-null."
+}
    • removedOutput schema / properties / count
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Rows returned."
-}
    • addedOutput schema / properties / cursor
      Added value: +{
+  "description": "Next page (detail full)."
+}
    • addedOutput schema / properties / delayed
      Added value: +{
+  "description": "Set when not live."
+}
    • removedOutput schema / properties / matches
      Removed value: -{
-  "anyOf": [
-    {
-      "items": {},
-      "type": "array"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "symbol, name, pair (when streamed), streamed, free, price, change_24h_pct, volume_24h_usd, market_cap_usd, rank."
-}
    • addedOutput schema / properties / next_tools
      Added value: +{
+  "description": "Follow-up calls {tool,args,why}.",
+  "items": {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  "type": "array"
+}
    • removedOutput schema / properties / query
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "The query as searched."
-}
    • changedOutput schema / properties / summary / description
      Previous value: -"The answer in one plain sentence, computed from the fields below. Open the reply with this, then let the numbers back it up. Null only when there was nothing to summarise."New value: +"The answer in one sentence."
    • removedOutput schema / properties / total
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Total catalog matches."
-}
    • addedOutput schema / properties / truncated
      Added value: +{
+  "description": "Rows held back; see trimmed."
+}
  2. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds useful return-content context (covered status, free status, price, 24h change) and states 'Free', but it does not discuss pagination behavior, rate limits, or edge cases beyond what the parameter schema already mentions.

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?

The core action is front-loaded in a compact first sentence, and the description stays short overall. 'Free.' is slightly redundant with 'whether it is free', but the description earns its place by being efficiently scannable.

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?

For a read-only search tool with full schema coverage and an output schema, the description conveys the essential inputs and outputs: search by symbol/name, get canonical symbol, coverage, free status, price, and 24h change. It lacks explicit guidance about when to prefer a sibling like coin_brief, but the schema covers pagination and detail levels.

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 description coverage is 100%, with each parameter already having a meaningful description such as 'Next page: the cursor from the previous answer' and 'brief (default): the answer, key numbers and top rows.' The description mostly restates the query concept ('by symbol or name') rather than adding new parameter-level meaning, so the baseline score of 3 applies.

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?

The description opens with a specific verb and resource: 'Find a coin by symbol or name', and clearly states the lookup value: canonical symbol, coverage, free status, price, and 24h change. It does not explicitly name a sibling like coin_brief, so differentiation is conveyed functionally rather than by direct contrast.

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?

The description gives clear context for when to use this tool: when you need to resolve a coin by symbol or name and learn whether it is covered, free, and what price/change it has. It does not provide explicit exclusions or name alternative tools, so it stops short of full routing guidance.

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

All whale-data toolsInspect
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