Skip to main content
Glama

get_market

Returns the top crypto assets by market cap (price, market cap, volume, 24h and 7d change).

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many assets to return (1–250, default 50).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

There are no annotations, so the description must carry the behavioral burden. It discloses the returned fields, which is genuinely useful given there is no output schema, but it says nothing about data freshness, source, caching, snapshot behavior, or sort stability, all of which matter for market data. It is adequate but thin.

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?

One sentence with a parenthetical field list, front-loaded with the core purpose, and zero wasted words. The density is high without sacrificing readability.

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?

With no annotations and no output schema, the description is the only place that states which fields come back, which it does. Its gaps are limited to freshness and ordering, minor for a simple read-only leaderboard tool.

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 coverage is 100%, and the single 'limit' parameter is fully documented in the schema with its 1–250 range and default of 50. The description adds nothing about the parameter or about ordering, so the baseline of 3 is correct.

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 uses a clear verb and resource and names the returned fields (price, market cap, volume, 24h and 7d change), so there is no ambiguity about what the tool produces. However, it does not differentiate this tool from same-domain siblings such as get_global_market, get_asset, or get_metrics; an agent must infer the boundary itself.

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

Usage Guidelines3/5

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

'Top crypto assets by market cap' implies the use case: a ranked leaderboard. It never says when to prefer this tool over get_global_market for aggregate data or get_asset for a single asset, and it gives no exclusions or prerequisites. The guidance is only implied.

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