Skip to main content
Glama
cmc-market-agent

cmc-market-agent

by melatim80186

get_quote

Retrieve current price, 24h/7d change, volume, and market cap for one or more cryptocurrencies by symbol to compare market data.

Instructions

Latest price, 24h/7d change, volume and market cap for one or more coins by symbol (e.g. BTC, ETH, SOL). Uses CMC endpoint /v1/cryptocurrency/quotes/latest.

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": {
      "symbols": "<symbols>"
    },
    "name": "get_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
convertNoFiat currency, default USD
symbolsYesCoin symbols, e.g. ["BTC", "ETH"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral burden. It does disclose the payload shape (price, 24h/7d change, volume, market cap) and names the upstream CMC endpoint, which is useful traceability, but it says nothing about rate limits, behavior on invalid/unknown symbols, or currency conversion defaults beyond what the schema already states.

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, front-loaded with what the tool returns and followed by the implementation source. Nothing is redundant or padded.

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 two-parameter read tool with full schema coverage and no output schema, the description covers purpose and returned fields adequately, partially compensating for the absent output schema. The remaining gap is edge-case behavior for unknown symbols or partial results.

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 both parameters are already documented in-schema, making 3 the baseline. The description reinforces the symbols parameter with concrete ticker examples (BTC, ETH, SOL) and confirms multi-coin batching, but adds no meaning for the convert parameter.

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 (fetch latest price) and resource (coin quotes) and enumerates the returned fields: price, 24h/7d change, volume, market cap. That field list implicitly separates it from siblings like get_ohlcv (candles) and search_coin (lookup), but no sibling is named explicitly, so differentiation is inferential rather than stated.

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 phrase 'for one or more coins by symbol' implies the calling context (you must already know the ticker) and signals batch usage, but there is no explicit when-to-use guidance, no statement of when to prefer search_coin first, and no note on what happens with an unknown symbol.

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