Skip to main content
Glama

Coinmarketcap Metadata

coinmarketcap_metadata
Read-onlyIdempotent

Static coin metadata, logo, description, website, social links.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "BTC,ETH"
    },
    "name": "coinmarketcap_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoComma-separated CMC IDs
symbolNoComma-separated tickers

Output Schema

NameRequiredDescriptionDefault
dataNoCryptocurrency metadata keyed by symbol or ID
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that: no note on rate limits, authentication, pagination, or what happens when neither id nor symbol is supplied (both are optional).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded, but it is a sentence fragment with no verb, so the brevity comes at the cost of clarity rather than from efficient editing. A short rewrite with a verb and one routing sentence would fit in the same space.

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

Completeness2/5

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

An output schema exists, so return values need not be described, and the annotations cover safety. However, for a tool with zero required parameters and two alternative lookup keys, the description never explains selection between id and symbol or the consequence of passing neither, leaving real gaps.

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 (comma-separated CMC IDs and comma-separated tickers) are already documented in the schema, and the examples show batching. The description adds no meaning about id-vs-symbol precedence or batching behavior, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a noun phrase enumerating returned fields (logo, description, website, social links) rather than a verb+resource statement. It does implicitly signal static reference data as opposed to price data, which is a meaningful distinction, but there is no verb and no explicit statement of what the tool does.

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?

There is no when-to-use guidance at all: nothing tells the agent to prefer this over coinmarketcap_quotes, coinmarketcap_category, or global_metrics, and nothing explains that id or symbol lookup selects the record. The only implicit hint is the word 'static'.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.