Skip to main content
Glama
tsetmc-mcp

tsetmc-mcp

by sepehr071

Stock quote

ts_get_quote
Read-onlyIdempotent

Fetch current price, daily range, volume, and key facts for a Tehran Stock Exchange instrument by ticker, exact name, or ins_code.

Instructions

Latest price, daily range, volume and key facts of one instrument on the Tehran Stock Exchange.

Use ts_order_book for bids and asks, ts_price_history for earlier days.

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": {
      "symbol": "<symbol>"
    },
    "name": "ts_get_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesTicker, exact name or ins_code, e.g. 'فولاد'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • changedInput schema / properties / symbol / description
      Previous value: -"Ticker or exact name, e.g. 'فولاد', 'وبملت', or a numeric ins_code."New value: +"Ticker, exact name or ins_code, e.g. 'فولاد'."
  2. First observedv0.1.1

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered by structured data. The description adds the substantive scope — a single instrument, TSE venue, snapshot rather than series — but says nothing about data freshness or delay, which matters for a live quote 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?

Two sentences, both load-bearing: the first defines the payload, the second handles disambiguation. Nothing is repeated from the title or schema, and the primary definition is front-loaded.

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 one fully documented parameter and no output schema, the description usefully enumerates what comes back (price, range, volume, key facts) so the agent knows the response shape. The only gap is the absence of any freshness or market-hours note for a real-time price 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?

Schema coverage is 100% and the symbol parameter already documents that a ticker, exact name, or ins_code is accepted with an example. The description's only added signal is that the tool resolves exactly one instrument, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific resource with enumerated contents (latest price, daily range, volume, key facts), scoped to one instrument on the Tehran Stock Exchange. It also names the two adjacent siblings it is not, so an agent can separate a snapshot quote from an order book or a historical series without opening a schema.

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 explicitly routes the agent away for two cases: depth data goes to ts_order_book, and prior sessions go to ts_price_history. The positive case (use this for the current snapshot) is implied rather than stated, and the remaining siblings (ts_search_symbols for ticker resolution, ts_market_movers, ts_indices) are not addressed.

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