Skip to main content
Glama

Market overview

market_overview
Read-only

List USDT perpetual contracts with price, 24h change, 24h volume and funding rate, sorted by volume, change or funding.

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

NameRequiredDescriptionDefault
sortNovolume
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description usefully discloses the returned field set and that results are sorted, but says nothing about the default result cap, whether this is a point-in-time snapshot, or refresh/rate behavior.

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?

A single front-loaded sentence with no filler: resource first, then returned fields, then ordering. It could have spent those same words clarifying the enum directions and the result cap rather than restating only three sort keys.

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?

Without an output schema, the description does the work of naming the returned fields, and for a simple read-only two-parameter tool that is nearly sufficient. The one real gap is the unmentioned 'limit' semantics, which an agent tuning result size would need.

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 0%, so the description must carry parameter meaning, and it partially does by naming three sort dimensions ('volume, change or funding'). However it omits the ascending variants (change_asc, funding_asc) present in the enum and never mentions the 'limit' parameter or its default of 20 / max of 100.

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?

States a specific verb ('List') and resource ('USDT perpetual contracts') plus the four fields returned, so an agent immediately knows this is a market-wide perp screener. It does not explicitly distinguish itself from siblings like coin_snapshot, so it lands at 4 rather than 5.

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 statement of when to use this versus alternatives (e.g. a single-coin lookup or a market report), and no prerequisites or exclusions. The market-wide scope only weakly implies 'use this for screening', leaving routing to inference.

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