Skip to main content
Glama

Range

range_stats
Read-only

Period range from daily candles: high and low with their UTC dates, % change over the period, % from the high and from the low, and bar coverage. period 7d, 30d, 90d or 1y; market spot (default) or futures. Free.

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>",
      "period": "<period>",
      "market": "<market>"
    },
    "name": "range_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
marketYesspot
periodYes
symbolYes

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?

With readOnlyHint and openWorldHint already declaring the safety profile, the description usefully adds that results derive from daily candles (a real resolution limit) and that the tool is 'Free' (a cost trait absent from annotations). It does not state what 'bar coverage' means or how sparse data is handled, so the added behavioral context is helpful but shallow.

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?

The payload is front-loaded in one dense sentence, followed by a short parameter/price fragment; almost every clause carries information. The telegraphic 'Free.' ending and list-style phrasing are terse but not padded.

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 three-parameter read-only tool with no output schema, the description does the heavy lifting by naming the returned fields, the data source, and the cost. Gaps remain around symbol format and behavior when candle data is incomplete, but nothing critical to calling it is missing.

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 0%, so the description must carry parameter meaning. It restates the period values (7d/30d/90d/1y) and the market choice including the spot default, which is largely redundant with the enums, and says nothing about the required 'symbol' parameter (format, ticker convention, 40-char cap).

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 computation ('period range from daily candles') and enumerates exactly what comes back (high/low with UTC dates, % change, % from high/low, bar coverage). An agent can tell this is a range-statistics tool, though it never contrasts itself with siblings such as get_price or get_structure.

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 when-to-use guidance and no naming of alternatives; the only real steering is the word 'Free', which is a cost signal rather than a routing rule. An agent must infer that this is the tool for period ranges and is given no exclusions or prerequisites.

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