Skip to main content
Glama
tgju-mcp

tgju-mcp

by sepehr071

Search symbols

tj_search_symbols
Read-onlyIdempotent

Search TGJU symbols by name or code in Persian or English to find unknown market symbols, then use the returned symbol for price or history lookups.

Instructions

Find TGJU symbols by name.

Use when the symbol is unknown; pass a result's symbol to tj_get_prices or tj_price_history.

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": {
      "query": "<query>"
    },
    "name": "tj_search_symbols"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax matches.
queryYesName or code, Persian or English, e.g. 'سکه امامی', 'brent'.
scopeNointernal = Iranian markets, global = world markets and pairs, crypto = coins.internal

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.0
    • changedInput schema / properties / limit / description
      Previous value: -"Max matches (the site returns at most 10)."New value: +"Max matches."
    • changedInput schema / properties / query / description
      Previous value: -"Name or code, Persian or English, e.g. 'سکه امامی', 'bitcoin', 'brent'."New value: +"Name or code, Persian or English, e.g. 'سکه امامی', 'brent'."
    • changedInput schema / properties / scope / description
      Previous value: -"internal = Iranian markets (gold, coins, currencies, funds), global = world markets and pairs, crypto = coins."New value: +"internal = Iranian markets, global = world markets and pairs, crypto = coins."
  2. First observedv0.1.0

TDQS

A4.2/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 the safety profile is covered. The description adds a genuinely useful behavioral fact not in structured data: results carry a `symbol` field intended to be passed downstream, which tells the agent this is a resolution step rather than a data-fetch step. It does not mention result ordering or what an empty/ambiguous match looks like.

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, zero filler, with the purpose front-loaded and the agent's next step attached immediately after. Nothing repeats the schema or annotations.

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?

There is no output schema, and the description partially compensates by disclosing that each result exposes a `symbol` for reuse. For a simple three-parameter search tool whose annotations and schema are rich, that is nearly complete; only the shape of the remaining result fields is left implicit.

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%, so `query`, `limit` and `scope` (including the internal/global/crypto enum and even a Persian example) are already fully documented in the schema. The description adds no additional meaning beyond that baseline; it never mentions scope or the 10-result cap.

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?

"Find TGJU symbols by name" gives a specific verb (find) and resource (symbols), and the second sentence makes clear this is the lookup tool that produces a `symbol` identifier consumed by other tools. That distinguishes it cleanly from tj_get_prices, tj_price_history, and the category-browsing siblings.

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 states the triggering condition explicitly ("Use when the symbol is unknown") and names the two follow-up tools that consume its output, which is genuine routing guidance. It stops short of naming alternatives for discovery (e.g., tj_list_categories / tj_category_table for browsing) or saying what to do if the query already returns an exact known code.

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