Skip to main content
Glama

get_volume_stats

Summarize candle volumes and compute chronological hourly or daily IST bucket totals for a market symbol within a specified time range.

Instructions

Summarize candle volumes and chronological hourly or daily IST bucket totals.

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

Input Schema

NameRequiredDescriptionDefault
argumentsYes

Output Schema

NameRequiredDescriptionDefault
bar_countYes
total_volumeYes
average_volumeYes
maximum_volumeYes
minimum_volumeYes
volume_by_bucketYes
average_bucket_volumeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden and does disclose that aggregation is by candle volume and chronological hourly or daily IST buckets. However, it does not describe missing-data handling, error behavior, or other operational context beyond the basic aggregation semantics.

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 filler. It efficiently states the core action and the bucketing behavior.

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?

For a read-only stats summarization tool with an output schema and parameter descriptions in the schema, the description is minimally sufficient to support invocation. It remains incomplete for an agent that needs to choose between this and sibling stats tools, since no routing guidance is provided.

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?

The nested schema already documents symbol, start_datetime, end_datetime, and bucket, including the hourly/daily enum and IST daily buckets. The description reinforces the bucket granularity and chronological nature but does not add substantive meaning beyond what the schema provides.

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 specific verb and resource: summarize candle volumes and produce hourly or daily IST bucket totals. It is clear what the tool does, but it does not explicitly distinguish itself from siblings such as intraday_stats or get_bars.

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 guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. The intended use is only implied by the word summarize and the candle-volume scope.

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