Skip to main content
Glama
cmc-market-agent

cmc-market-agent

by melatim80186

get_global_metrics

Retrieves whole-market cryptocurrency totals, including market cap, 24-hour volume, BTC/ETH dominance, and active coin/exchange counts, with optional fiat conversion.

Instructions

Whole-market totals: total market cap, 24h volume, BTC/ETH dominance, active coins and exchanges. Uses CMC endpoint /v1/global-metrics/quotes/latest.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_global_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
convertNoFiat currency, default USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 behavioral burden. The verb 'get' plus 'whole-market totals' makes the read-only, non-destructive nature clear, and the CMC endpoint reference adds useful provenance about the data source. However, it says nothing about authentication requirements, rate limits, caching/freshness of the data, or error behavior.

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?

Two sentences, front-loaded with the returned fields and no redundant phrasing. The trailing endpoint reference is marginally useful provenance rather than filler, though it could be dropped without losing call-critical information.

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 zero-required-parameter read tool with no output schema, enumerating the returned fields in the description is exactly the right compensation, and the single optional parameter is fully covered by the schema. Only operational details (freshness, limits) are absent, which is a modest gap given the tool's simplicity.

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% — the single 'convert' parameter is already documented in the schema as 'Fiat currency, default USD'. The description adds no further meaning about accepted currency codes or how conversion affects the returned figures, so the schema does all the work and baseline 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?

States a specific resource and scope: 'Whole-market totals' followed by an enumeration of exactly what is returned (market cap, 24h volume, BTC/ETH dominance, active coins and exchanges). The 'whole-market' framing implicitly separates it from per-coin siblings like get_quote or get_ohlcv, but no sibling is named explicitly.

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?

There is no explicit when-to-use or when-not-to-use guidance and no alternative is named. Usage is only implied by the word 'global', which suggests an aggregate overview rather than a single-asset lookup — an agent must infer that routing decision itself.

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