quotesLatest market quotes for one or more cryptocurrencies. Identify by symbol (e.g. "BTC,ETH") OR by id (CMC numeric IDs).
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Comma-separated CMC IDs | |
| symbol | No | Comma-separated tickers (e.g. "BTC,ETH,SOL") | |
| convert | No | Target currency (default USD) |
| Name | Required | Description | Default |
|---|---|---|---|
| data | No | Cryptocurrency quote data keyed by symbol or ID | |
| status | No |
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {
+ "symbol": "BTC,ETH,SOL"
+ },
+ {
+ "convert": "EUR",
+ "id": "1,1027,5426"
+ }
+]Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "data": {
+ "description": "Cryptocurrency quote data keyed by symbol or ID",
+ "type": "object"
+ },
+ "status": {
+ "properties": {
+ "credit_count": {
+ "description": "API credits consumed",
+ "type": "integer"
+ },
+ "elapsed": {
+ "description": "Elapsed milliseconds",
+ "type": "integer"
+ },
+ "error_code": {
+ "description": "Error code (0 for success)",
+ "type": "integer"
+ },
+ "error_message": {
+ "description": "Error message if applicable",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "timestamp": {
+ "description": "ISO timestamp of the quote",
+ "type": "string"
+ }
+ },
+ "type": "object"
+ }
+ },
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint. The description adds 'latest' implying freshness and covers parameter requirements, which aligns and slightly extends transparency. No contradiction with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence that communicates the core purpose and key differentiators (by symbol or id). It is optimally concise with no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the presence of an output schema and complete parameter descriptions, the description sufficiently outlines what the tool returns ('latest market quotes'). No additional context needed for this simple query tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so parameters are well-documented. The description repeats the two identification methods but adds no new semantic meaning beyond the schema. The examples in schema already illustrate usage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool provides 'latest market quotes' for cryptocurrencies and specifies two identification methods (symbol or id). The verb and resource are explicit, and the description distinguishes the tool from siblings like 'listings_latest' or 'global_metrics' covering different data.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage when needing up-to-date quotes but provides no when-not or alternative guidance. With many sibling tools, explicit usage context would help, but the current phrasing is minimally adequate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.