StockMap

Crypto map

crypto_map

Read-onlyIdempotent

The crypto market on StockMap's coin map: the 250 largest coins by market value (CoinGecko), grouped by theme (layer 1, stablecoins, exchange tokens, memes and more), with Bitcoin's share of all crypto, each theme's move over 24 hours and the biggest moves. Its card draws the coins as StockMap's heatmap, Bitcoin to scale and the stablecoins at the edge, or as bubbles, live. Market data with no call on any coin. Each answer carries the stamp, the sources and the not-advice line.

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

Input Schema

Name	Required	Description	Default
`view`	No	How the card draws the coins: "map", StockMap's coin map, or "bubbles", the biggest coins as bubbles sized by market value	map

Output Schema

Name	Required	Description	Default
`up`	Yes	The biggest 24-hour moves up
`down`	Yes	The biggest 24-hour moves down
`view`	No		map
`as_of`	No	The prices' time, ISO 8601 UTC
`coins`	Yes
`themes`	Yes	Biggest first
`page_url`	No		https://stockmap.io/crypto
`market_cap`	Yes	As the page writes it ($2.76T)
`not_advice`	No		We don't tell you what to buy. Research and education, not investment advice.
`bitcoin_price`	No
`bitcoin_share_pct`	No	Bitcoin's share of all crypto's market value, in %
`bitcoin_change_24h_pct`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

B3.2/5.0

Behavior3/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds useful context that the data is live, contains no recommendation, and includes stamps, sources, and a not-advice line, but it does not describe update frequency, caching, or other operational behavior.

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?

The description is front-loaded with the core purpose, but it is dense and somewhat ornate. Phrases such as 'Bitcoin to scale and the stablecoins at the edge' add useful visualization detail, yet the overall paragraph is longer than necessary for a one-parameter tool.

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

Completeness4/5

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

Given the output schema, annotations, and fully described parameter, the description is largely complete: it covers data scope, visualization modes, disclaimers, and the non-advice nature of the content. The main missing piece is routing guidance against sibling tools.

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?

The single view parameter is fully documented in the schema with an enum and descriptions for map versus bubbles. The description mentions both representations but adds no extra syntax or behavioral meaning beyond what the schema already provides, so the baseline of 3 applies.

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

Purpose4/5

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

The description states a specific resource and scope: the 250 largest coins by market value, grouped by theme, with Bitcoin dominance and 24-hour moves. It is clear what the tool returns, but it does not explicitly distinguish itself from related crypto siblings such as crypto_today or is_it_altseason.

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 explicit guidance on when to use this tool versus alternatives like crypto_today, crypto_stocks, or is_it_altseason. The visualization context implies it is for a visual market overview, but no exclusions or selection criteria are provided.

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

All StockMap tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?