Skip to main content
Glama
cmc-market-agent

cmc-market-agent

by melatim80186

get_ohlcv

Fetch daily OHLCV candles (open, high, low, close, volume, market cap) for a coin over the last N days to analyze price and volume trends.

Instructions

Daily OHLCV candles (open/high/low/close/volume/market cap) for one coin over the last N days. Uses CMC endpoint /v2/cryptocurrency/ohlcv/historical.

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": {
      "symbol": "<symbol>"
    },
    "name": "get_ohlcv"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoNumber of days, default 7
symbolYesCoin symbol, e.g. "BTC"

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 carries the full burden, but it does add real value by disclosing the upstream endpoint (/v2/cryptocurrency/ohlcv/historical), the daily granularity, and the exact returned fields. It omits auth/rate-limit expectations, error behavior for an unknown symbol, timezone of candle boundaries, and whether the most recent candle is partial.

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 data shape and scope front-loaded and the provenance detail second; nothing is padded or redundant.

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 no output schema, the description covers data fields, granularity, and scope well enough to call it correctly. The only meaningful gap is the absence of any note on failure modes or partial/latest-candle behavior, which would matter for a market-data tool.

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%, so both parameters (symbol, days) are already documented in the schema, and the description only restates them as 'one coin' and 'last N days'. The baseline of 3 applies since the text adds no format or edge-case detail beyond the schema.

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 names the exact resource (daily OHLCV candles with open/high/low/close/volume/market value) and scopes it to a single coin over the last N days, which is specific enough to separate it from siblings like get_quote or get_listings. It stops short of explicitly naming when a sibling such as get_quote would be preferred, so it lands just below top marks.

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?

Usage is only implied: the phrase 'for one coin over the last N days' signals the historical-daily use case, and the mention of the CMC historical endpoint reinforces it. There is no explicit statement of when to use this versus a spot-quote tool, and no exclusions or prerequisites are given.

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