metadataStatic coin metadata — logo, description, website, social links.
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Comma-separated CMC IDs | |
| symbol | No | Comma-separated tickers |
| Name | Required | Description | Default |
|---|---|---|---|
| data | No | Cryptocurrency metadata keyed by symbol or ID | |
| status | No |
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {
+ "symbol": "BTC,ETH"
+ },
+ {
+ "id": "1,1027"
+ }
+]Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "data": {
+ "description": "Cryptocurrency metadata 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",
+ "type": "string"
+ }
+ },
+ "type": "object"
+ }
+ },
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the description's mention of 'static' adds marginal context. No contradictions. The description could elaborate on response format or edge cases (e.g., missing parameters), but the presence of an output schema mitigates this.
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?
Single sentence, no wasted words. Front-loaded with the key idea ('Static coin metadata') and immediately specifies what it includes. Perfectly concise.
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 rich annotations and presence of an output schema, the description adequately covers the tool's functionality. It could mention that both parameters are optional (returning all coins), but the schema's lack of required params implies this, and the description is otherwise complete for a simple data retrieval 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 coverage is 100%, with clear descriptions for both parameters (comma-separated IDs/tickers). The description adds no additional meaning beyond the schema, so baseline 3 applies.
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 identifies the tool's purpose: retrieving static coin metadata such as logo, description, website, and social links. It distinguishes from sibling tools like quotes or categories, but could be more explicit about the action (e.g., 'get'). The verb 'metadata' is implied by context.
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 provides no guidance on when to use this tool over alternatives (e.g., quotes, categories, global_metrics). It does not specify when not to use it or mention use cases. The agent must infer usage from the tool name and description alone.
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.