Skip to main content
Glama
cmc-market-agent

cmc-market-agent

by melatim80186

search_coin

Resolve a coin symbol or name to its CoinMarketCap ID, slug, and rank so you can look up market data and OHLCV history when only the ticker or name is known.

Instructions

Resolve a coin symbol or name to its CoinMarketCap id, slug and rank. Use before get_ohlcv when you only know a symbol. Uses CMC endpoint /v1/cryptocurrency/map.

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_coin"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSymbol or name, e.g. "BTC" or "bitcoin"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses the returned fields and the underlying CMC endpoint, but does not explain matching behavior, ambiguity handling, rate limits, or error cases.

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 description is short and front-loaded with the core resolve action. The endpoint detail is somewhat implementation-focused but does not undermine clarity or add significant bloat.

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 simple one-parameter lookup tool with no output schema, the description provides enough information to invoke it and understand the primary returned fields. It is not fully complete because it omits how ambiguous queries or multiple matches are handled.

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%, and the single query parameter is well documented in the schema with examples. The description only restates that the query can be a symbol or name, adding no new parameter semantics.

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?

The description states a specific verb and resource: resolve a coin symbol or name to CoinMarketCap id, slug, and rank. It directly distinguishes the tool from retrieval tools like get_ohlcv by framing it as an identifier resolution step.

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?

It gives clear usage guidance: use before get_ohlcv when only a symbol is known. It does not explicitly describe when not to use it, such as when an id is already available, but the intended context is clear.

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