Skip to main content
Glama

AINDEX

Size and range of a coin or stock

market_overview
Read-only

For a coin (CoinGecko): market cap and rank, FDV, volume, circulating, total and max supply, all-time high and low with dates, 24h range, moves over 7d, 30d and a year. For a stock or ETF (Nasdaq): market cap, 52-week range, sector, one-year target, volume, dividend.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "market_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely useful context beyond that: the underlying data providers (CoinGecko for coins, Nasdaq for stocks), which tells the agent about coverage boundaries and which asset types are supported. It says nothing about data freshness, rate limits, or what happens for an unknown/ambiguous symbol, so it stops short of a 4.

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?

Two tight parallel sentences, front-loaded by asset class, with zero filler. The trade-off is that the content is a raw field inventory rather than prioritized guidance, but nothing is wasted.

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

Completeness3/5

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

With no output schema, listing the returned fields is the right move and largely does the job for a single-symbol lookup. However, for a tool whose only input is a free-form symbol with an unusual pattern and no schema documentation, the missing input-format guidance leaves a real hole an agent would hit on first call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one parameter with 0% schema description coverage, so the description carries the full burden — and it never mentions the symbol at all. The schema pattern permits colons, slashes and equals signs (suggesting identifiers like 'NASDAQ:AAPL' or pair-style strings), yet the description gives no format examples, no case rules, and no indication of how a coin vs a stock symbol is disambiguated.

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 names the resource (market overview) and enumerates exactly what is returned, split by asset class — CoinGecko coin metrics vs Nasdaq stock/ETF metrics. An agent can tell what it gets back, though the purpose is framed as a field list rather than a verb, and it never contrasts itself with lookalike siblings such as get_stock_quotes or get_asset.

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?

The description states the two asset classes it handles, which implicitly scopes usage to 'when you want a snapshot for a coin or stock.' But it gives no when-to-use versus alternatives (get_stock_quotes, get_asset, market_dossier, get_token_market), no exclusions, and no prerequisites such as whether the symbol must already be known.

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.

Resources