Skip to main content
Glama

compare_symbols

Compare two or more NSE-listed symbols across shared daily trading dates using daily metrics for a specified date range.

Instructions

Compare at least two symbols using daily metrics on their common trading dates.

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

Input Schema

NameRequiredDescriptionDefault
argumentsYes

Output Schema

NameRequiredDescriptionDefault
symbolsYes
common_trading_daysYes
common_trading_datesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that comparison is limited to daily metrics and common trading dates, but it does not state read-only safety, error behavior when no dates overlap, or the configured symbol cap.

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 definition is a single front-loaded sentence with no filler. Every clause contributes a constraint or scope detail.

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. Still, the description does not clarify what comparison metrics are produced or when this tool is preferable to siblings, leaving moderate gaps for a multi-symbol analytical tool.

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 describes symbols, interval, start_datetime, and end_datetime in detail, including the daily-only interval and inclusive ISO-8601 timestamps. The description reinforces the minimum of two symbols and daily interval but adds no additional syntax or date-range semantics beyond the schema.

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 verb and resource: compare symbols using daily metrics on common trading dates. It also adds the key constraint of at least two symbols. It does not explicitly distinguish itself from siblings such as compute_indicators 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'at least two symbols' and 'common trading dates' implies usage for multi-symbol comparison over overlapping periods. However, there is no explicit guidance on when to use this instead of get_bars or compute_indicators, nor any stated exclusions.

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