Skip to main content
Glama
tsetmc-mcp

tsetmc-mcp

by sepehr071

Market movers

ts_market_movers
Read-onlyIdempotent

Fetch daily traded instruments from Tehran's bourse, Fara Bourse, rights, or bonds, sorted by gain, loss, volume, value, or trade count.

Instructions

Top traded instruments of a market today, ranked by gain, loss, volume, value or trade count.

Only traded instruments. limit_up/limit_down = stuck at the daily limit. Pass a row's symbol to other ts_ tools.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows.
marketNobourse = Tehran shares, farabourse = Fara Bourse shares, plus rights and bonds.bourse
sort_byNogain/loss = last-trade change vs yesterday, value = Rial traded.gain

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.0
    • changedInput schema / properties / limit / description
      Previous value: -"Max rows (30 keeps the reply under 15 KB)."New value: +"Max rows."
    • changedInput schema / properties / market / description
      Previous value: -"bourse = Tehran Stock Exchange shares, farabourse = Iran Fara Bourse shares, rights = rights issues, bonds."New value: +"bourse = Tehran shares, farabourse = Fara Bourse shares, plus rights and bonds."
    • changedInput schema / properties / sort_by / description
      Previous value: -"gain/loss = biggest last-trade change vs yesterday, volume = shares traded, value = Rial traded, trades = trade count."New value: +"gain/loss = last-trade change vs yesterday, value = Rial traded."
  2. First observedv0.1.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is covered. The description adds real behavioral content beyond that: results are restricted to traded instruments, the window is 'today', and limit_up/limit_down mark instruments stuck at the daily limit. It does not mention ordering stability beyond sort_by or what an empty result means.

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 purpose, then scope caveats, then downstream chaining advice. No filler or repetition.

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?

For a 3-parameter, no-output-schema read tool with full annotation coverage, the description supplies the key domain semantics: traded-only filtering, today's window, and the limit flag fields. A brief note on ordering behavior or what fields rows contain would make it fully self-sufficient, but nothing essential is missing.

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 description coverage is 100%, with enum values and defaults documented for market and sort_by, so the baseline is 3. The description reinforces the sort modes and adds the meaning of limit-related row fields, but adds little parameter syntax or constraint information that the schema does not already carry.

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 resource and scope: 'Top traded instruments of a market today, ranked by gain, loss, volume, value or trade count.' An agent immediately knows this is a ranked movers listing. It does not explicitly distinguish itself from siblings like ts_indices or ts_search_symbols, but the 'top traded, ranked' framing is distinctive enough.

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?

Usage is implied rather than stated: the tool shows top movers for a market today. The only routing guidance is downstream ('Pass a row's `symbol` to other ts_ tools'), which tells the agent what to do after calling, not when to prefer this over alternatives. No exclusions or prerequisites are given.

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