Skip to main content
Glama
cmc-market-agent

cmc-market-agent

by melatim80186

get_market_brief

Retrieve a one-call crypto market brief with top coins by market cap, biggest gainer/loser, Fear & Greed index, and total market cap for quick morning updates.

Instructions

One-call morning brief: top coins by market cap, biggest gainer/loser, Fear & Greed index and total market cap. Composed from the listings, gainers-losers, fear-greed and global-metrics endpoints.

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

Input Schema

NameRequiredDescriptionDefault
top_nNoHow many top coins, default 5

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose the most important behavioral trait: this is a composed/derived result built from four named endpoints, implying its values will match those sources. It enumerates the returned sections, effectively standing in for the absent output schema. It does not state caching/freshness or error behavior for a possibly expensive fan-out call, which keeps it below 5.

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

Conciseness5/5

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

Two sentences, both front-loaded and dense: the first says what you get, the second says where it comes from. No filler, no restatement of the tool name in isolation.

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?

For a one-parameter, read-only aggregate with no output schema, the description covers purpose, composition, and result sections, which is most of what an agent needs. The main residual gap is that it never describes the shape of the four sections or whether values are point-in-time snapshots.

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% and there is a single optional integer parameter (top_n, 1-20, default 5) fully documented in the schema. The description only alludes to it via "top coins" and adds no constraints or defaults beyond that, so the baseline of 3 applies.

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 names a specific resource (a composite morning brief) and enumerates exactly what it contains: top coins by market cap, biggest gainer/loser, Fear & Greed, and total market cap. It also identifies the four underlying endpoints, which lets an agent see immediately that this aggregates the get_listings / get_gainers_losers / get_fear_greed / get_global_metrics siblings rather than duplicating one of them.

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

Usage Guidelines4/5

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

The phrase "One-call morning brief" plus the endpoint list makes the intended use clear: fetch a market overview in a single call instead of fanning out to four separate tools. There is no explicit when-not-to-use guidance (e.g., use get_quote for a single coin), so it stops short of full alternative routing.

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