Skip to main content
Glama
cse-mcp

cse-mcp

Index history

get_index_history
Read-onlyIdempotent

Retrieve historical price data for a market or sector index over selected periods, including today's minute data or 1-week to 1-year ranges.

Instructions

History of a market or sector index. index can be "ASPI", "S&P SL20", a sector name/symbol from get_sector_indices (e.g. "Banks", "BNK") or its numeric index_id. period: "today" (minute data), "1w", "1m", "3m", "1y".

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_index_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexNoASPI
periodNo1m
max_pointsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered by structured data. The description's added value is the granularity disclosure that "today" returns minute data, but it says nothing about how max_points downsamples or trims the series, which is a meaningful behavioral trait for a time-series tool.

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?

Three short sentences, front-loaded with what the tool returns, then the accepted input values, then the period options. No filler, no restatement of the title, and the backticked literals make the accepted values scannable.

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?

With an output schema present, return-value documentation is correctly omitted, and the description covers two of three parameters in detail. The only substantive omission is the meaning/effect of max_points (default 120), which an agent calling this for charting or analysis would want to understand.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the burden and largely does: it enumerates accepted index values (ASPI, S&P SL20, sector name, sector symbol, numeric index_id) and lists all period enum values with a granularity note for "today". The third parameter, max_points, is never mentioned, leaving one gap.

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?

States a specific verb+resource ("History of a market or sector index") and immediately scopes the resource to indices rather than individual stocks, which implicitly separates it from get_price_history. It doesn't explicitly name a sibling alternative, so it stops short of the top mark.

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 cross-reference to get_sector_indices tells the agent where valid sector names/symbols come from, which is real routing guidance. However, there is no statement of when to prefer this over get_price_history or get_market_overview, and no prerequisites or exclusions.

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