Skip to main content
Glama
tsetmc-mcp

tsetmc-mcp

by sepehr071

Order book

ts_order_book
Read-onlyIdempotent

Fetch the five best bid and ask levels—price, volume, and order count—for a single instrument to assess market depth on Tehran exchanges.

Instructions

Best five bid and ask levels (price, volume, order count) of one instrument.

Empty outside trading hours. Ask price 0 = buy queue (no sellers), bid price 0 = sell queue.

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

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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavior: the result is truncated to five levels per side, and the 0-price sentinel means an empty queue on that side rather than bad data. It does not say whether the snapshot is real-time or delayed, which matters for an order book.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the resource description before the caveats, and no filler. The sentinel notation is telegraphic but decodes cleanly.

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, the description carries the burden of describing the return value and does so concretely: five levels per side, each with price, volume and order count. The two non-obvious failure modes (empty outside trading hours, zero-price queues) are covered, leaving only data freshness unaddressed.

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 coverage is 100% for the single symbol parameter, including the accepted forms (ticker, exact name, ins_code) and an example. The description adds nothing about the parameter, so the baseline applies rather than extra credit.

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 names the exact resource and its shape: the best five bid and ask levels with price, volume and order count for one instrument. That is far more specific than a sibling like ts_get_quote, though it never explicitly contrasts itself with any sibling tool.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative, so the agent must infer that this tool is for depth rather than last-price data. The 'Empty outside trading hours' note is a useful implicit usage signal, telling the agent when a valid call will return nothing.

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