Retrieve CC market statistics including total supply, circulating supply, burn rate, and implied USDC exchange rate to assess the health of the CC economy, no API key required.
Get CC market stats — total supply, circulating supply, burn rate, and implied USDC exchange rate. Tracks the health of the CC economy. No api_key required.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It indicates a read-only operation (Get) and mentions no authentication required, which is helpful. However, it does not disclose rate limits, data freshness, error modes, or other behavioral characteristics beyond the basic safety profile.
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?
Two sentences: the first is a clear, front-loaded statement of the tool's function, and the second adds complementary context. Every word earns its place with no redundancy or filler.
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 no parameters, no output schema, and no annotations, the description sufficiently covers what the tool does, what data it returns, and the fact that no API key is required. Nothing crucial is missing for a simple stats endpoint.
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?
The tool has zero parameters, so the baseline is 4 per the rubric. The description adds value by listing the returned stats (total supply, etc.), compensating for the lack of output schema. No further parameter documentation is needed.
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?
Clearly states it retrieves CC market stats (total supply, circulating supply, burn rate, implied USDC exchange rate). The description uses a specific verb ('get') and resource ('CC market'), and the tool is distinct from sibling tools like get_cc_balance or get_cc_history which focus on individual or transactional 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 notes that it tracks the health of the CC economy, suggesting its use for market health assessment. It also explicitly states 'No api_key required', which is a usage condition. However, it does not specify when not to use this tool or mention alternatives among siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.