Skip to main content
Glama
tsetmc-mcp

tsetmc-mcp

by sepehr071

Market indices

ts_indices
Read-onlyIdempotent

Retrieve Tehran Stock Exchange total, sector, and market indices with market state, trading totals, and changes; filter by index name to focus on relevant benchmarks.

Instructions

TSE total index, market state and trading totals, plus every sector and market index with its change.

Pass an index name to ts_index_history for past values.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax indices, strongest first.
queryNoPart of an index name, e.g. 'بانک', 'هم وزن'. Omit for all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.0
    • changedInput schema / properties / limit / description
      Previous value: -"Max indices, strongest change first."New value: +"Max indices, strongest first."
    • changedInput schema / properties / query / description
      Previous value: -"Optional part of an index name, e.g. 'بانک', 'خودرو', 'شاخص کل', 'هم وزن'. Omit for all."New value: +"Part of an index name, e.g. 'بانک', 'هم وزن'. Omit for all."
  2. First observedv0.1.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so safety is covered. The description adds the substantive part the annotations cannot: the breadth of returned data (total index plus market state, trading totals, and all sector indices with changes), which matters since there is no output schema. It says nothing about result ordering or the 60-item cap, though the schema's "strongest first" note partially covers that.

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?

Two sentences, no filler. The return contents come first, followed by the disambiguation pointer, so the agent reads the purpose before the routing advice.

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 no output schema and no required parameters, the description carries the burden of describing what comes back, and it does so at a summary level while the schema handles the inputs. A note on whether all indices are returned in one response versus paged by `limit` would close the remaining gap.

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?

Schema coverage is 100%, so both `limit` and `query` are already documented with examples and defaults, establishing the baseline of 3. The description adds nothing about `query` syntax itself; its mention of an index "name" refers to a parameter of ts_index_history, not this tool's `query`, which could momentarily blur the two.

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 enumerates exactly what the tool returns: TSE total index, market state, trading totals, and every sector/market index with its change. That clearly separates it from ts_index_history (past values) and from symbol-level siblings like ts_get_quote. It lacks an explicit verb ("return"/"list"), so the action is inferred from a noun phrase 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 Guidelines4/5

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

It names the alternative tool explicitly: "Pass an index `name` to ts_index_history for past values," giving a clear routing rule for the historical case. It does not explicitly say "use this for the current index snapshot," and it does not address overlap with ts_market_movers or ts_get_quote, but the usage context is clear enough without exclusions.

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