Skip to main content
Glama

get_price_extremes

Find the highest high and lowest low, including their earliest timestamps, within a specified UTC date-time range for a market symbol.

Instructions

Find the highest high and lowest low, with their earliest timestamps, in a UTC range.

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": {
      "arguments": "<arguments>"
    },
    "name": "get_price_extremes"
  }
}

Input Schema

NameRequiredDescriptionDefault
argumentsYes

Output Schema

NameRequiredDescriptionDefault
lowest_lowYes
highest_highYes
range_absoluteYes
range_percentageYes
lowest_low_timestampYes
highest_high_timestampYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. The verb 'Find' implies a safe read-only operation and the return concept is clear, but it does not explicitly state read-only behavior, permissions, or handling of edge cases such as missing data.

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?

The description is a single front-loaded sentence with no wasted words. It states the computation and timestamp behavior directly.

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?

The tool is simple, and the output schema covers return values, so the description need not explain them. However, with no annotations and no usage guidance, it remains incomplete on when to choose this tool and on explicit read-only behavior.

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?

The description adds only 'in a UTC range' beyond the schema, which does not fully compensate for the reported 0% schema description coverage at the top level. It does not clarify symbol selection or inclusive timestamp semantics, despite those being essential to invocation.

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 a specific computation: highest high, lowest low, and their earliest timestamps within a UTC range. This clearly distinguishes it from generic bar, volume, or indicator tools, though it does not explicitly name a sibling alternative.

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 gives no guidance on when to use this tool versus siblings such as get_bars, get_volume_stats, or intraday_stats. It implies a use case by naming price extremes, but leaves selection to inference.

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