Wicked MCP server

market_overview

Read-onlyIdempotent

Retrieve global crypto stats including total market cap, 24-hour volume, and BTC/ETH dominance, or list top coins by market cap.

Instructions

[Trading Data API] Free, no signup required. CoinGecko global crypto stats (total market cap, 24h volume, BTC/ETH dominance) or top coins by market cap.

Example: /v1/market-overview

Use when you want global crypto stats: total market cap, 24h volume, BTC and ETH dominance. Not for a single asset's price (use price).

Behavior: read-only and free; no key or payment needed.

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": "market_overview"
  }
}

Input Schema

Name	Required	Description	Default
`view`	No	Optional. global (default) or coins.
`limit`	No	Optional (coins view). Number of coins (default 20, max 100).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Oct 3, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds useful context beyond annotations: it is free, requires no signup, and needs no key or payment. It does not describe rate limits or response format, so it falls short of a 5.

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 front-loaded and appropriately sized. It repeats the same stat list in the opening sentence and the 'Use when' sentence, which is a minor redundancy.

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

Completeness5/5

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

For a simple two-parameter read-only tool with full schema coverage and annotations, the description provides enough context: data source, use case, exclusion, auth/payment behavior, and the returned stat categories. Nothing essential for correct invocation is missing.

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 parameter documentation is already handled by the schema. The description implies the two views but does not add parameter names, defaults, or constraints beyond what the schema provides.

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

Purpose5/5

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

The description clearly states the resource and scope: CoinGecko global crypto stats or top coins by market cap. It explicitly distinguishes itself from the `price` sibling for single-asset queries, so an agent can select it without opening the schema.

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

Usage Guidelines5/5

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

It gives an explicit use case (global crypto stats such as market cap, volume, and dominance) and an explicit exclusion with the alternative: 'Not for a single asset's price (use price).' This leaves little ambiguity.

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

Deploy Server