CoinCap MCP Server

get_markets

Retrieve cryptocurrency market data to identify all exchange markets where a specific digital asset trades, enabling users to analyze trading venues and liquidity sources.

Instructions

Get market data for a specific cryptocurrency, showing all exchange markets where it trades

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

Input Schema

Name	Required	Description	Default
`baseId`	No	Base asset ID (e.g., 'bitcoin', 'ethereum')
`limit`	No	Max number of results (default: 100)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 26, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool 'gets' data, implying a read-only operation, but doesn't address other behavioral aspects such as rate limits, error handling, authentication needs, or response format. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 a single, efficient sentence that front-loads the core purpose ('Get market data for a specific cryptocurrency') and adds clarifying scope ('showing all exchange markets where it trades'). There's no wasted text, but it could be slightly more structured (e.g., by explicitly mentioning parameters) to achieve a perfect score.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (2 parameters, no output schema, no annotations), the description is minimally adequate. It covers the purpose and scope but lacks details on behavioral traits, usage guidelines, and output expectations. With no annotations or output schema, the description should do more to compensate, but it meets a basic threshold.

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?

The input schema has 100% description coverage, with clear documentation for both parameters (baseId and limit). The description adds no additional parameter semantics beyond what the schema provides, such as examples of baseId values or details on limit behavior. With high schema coverage, the baseline score of 3 is appropriate.

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 clearly states the tool's purpose with a specific verb ('Get') and resource ('market data for a specific cryptocurrency'), and it specifies the scope ('all exchange markets where it trades'). However, it doesn't explicitly distinguish this tool from its siblings (e.g., get_asset_by_id, get_rates), which would be needed for a score of 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like get_assets or get_rates. It mentions the scope ('all exchange markets') but doesn't clarify use cases, prerequisites, or exclusions, leaving the agent to infer usage from the tool name and parameters alone.

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

Deploy Server