Skip to main content
Glama

intraday_stats

Summarizes a symbol's IST trading session with OHLC, volume, VWAP, and returns for a given date.

Instructions

Summarize a symbol's session on an IST date, including OHLC, volume, VWAP, and returns.

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

Input Schema

NameRequiredDescriptionDefault
argumentsYes

Output Schema

NameRequiredDescriptionDefault
lowYes
highYes
openYes
vwapYes
closeYes
bar_countYes
total_volumeYes
last_timestampYes
absolute_returnYes
first_timestampYes
percentage_returnYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden. It discloses that the date is an IST calendar date, but says nothing about read-only vs mutating behavior, how non-trading days, holidays, or missing data are handled, or how returns are computed — all material for a market-data summarizer.

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 zero filler; the summary scope and the output fields are packed efficiently. It is appropriately sized, though it offers no structural separation between scope and returned content.

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?

An output schema exists, so return values need not be explained, and the description correctly avoids restating them. However, for a tool with no annotations and edge-case-sensitive market data, the omission of error, holiday, and read-only behavior leaves it only minimally complete.

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 description reinforces the two key parameter semantics (single symbol, IST trading date), but adds no format, range, or validation detail beyond what the input schema already states. It neither compensates for the reported coverage gap nor introduces ambiguity.

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 ('Summarize') on a specific resource ('a symbol's session on an IST date') and enumerates the contents (OHLC, volume, VWAP, returns), which implicitly separates it from siblings like get_bars or get_volume_stats. It stops short of naming any sibling explicitly, so differentiation is inferential rather than stated.

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 or when-not-to-use guidance, no mention of prerequisites, and no reference to alternatives such as get_bars or compare_symbols. An agent must infer the use case entirely from the purpose sentence.

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