Skip to main content
Glama

Coinmarketcap Quotes

coinmarketcap_quotes
Read-onlyIdempotent

Latest market quotes for one or more cryptocurrencies. Identify by symbol (e.g. "BTC,ETH") OR by id (CMC numeric IDs).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "BTC,ETH,SOL"
    },
    "name": "coinmarketcap_quotes"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoComma-separated CMC IDs
symbolNoComma-separated tickers (e.g. "BTC,ETH,SOL")
convertNoTarget currency (default USD)

Output Schema

NameRequiredDescriptionDefault
dataNoCryptocurrency quote data keyed by symbol or ID
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the either-symbol-or-id identification contract, but says nothing about data freshness, rate limits, or what happens with no identifier supplied.

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?

Two short sentences with the resource statement front-loaded and the identifier options immediately after. No filler, no restating of the title.

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?

An output schema exists, so return-value explanation is unnecessary, and the description covers both identification modes. The one notable gap is that with zero required parameters, the description never says whether omitting both symbol and id is valid or what the default behavior is.

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%, so the schema already documents all three parameters, establishing the baseline of 3. The description adds one genuinely useful semantic detail not in the schema: that symbol and id are alternative identification routes (use one OR the other).

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 and resource ("Latest market quotes for ... cryptocurrencies"), which clearly separates it from siblings like coinmarketcap_metadata or global_metrics. It stops short of explicitly naming a sibling to contrast with, so not a 5.

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 description implies the usage context (fetching current prices for one or more coins) and offers two identification modes, but gives no explicit when-to-use vs. when-not guidance or prerequisites. Usage is inferable rather than stated.

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.