Skip to main content
Glama
tgju-mcp

tgju-mcp

by sepehr071

Category price table

tj_category_table
Read-onlyIdempotent

Fetch a live TGJU category price table for gold, coin, currency, or crypto symbols, including price, change, and daily high/low/open values.

Instructions

Live price table of one TGJU group: price, change, day high/low/open per symbol.

Use for 'all gold prices', 'all coin prices'. Rial groups carry *_toman; crypto is USD; unit: mixed adds a unit per row. The crypto preset lists ~27,000 coins unordered: use tj_get_prices or tj_search_symbols.

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": {
      "category": "<category>"
    },
    "name": "tj_category_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows.
offsetNoRows to skip.
categoryYesPreset (gold, coin, coin_retail, currency, currency_government, currency_sana, currency_nima, crypto) or a folder id from tj_list_categories.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.0
    • changedInput schema / properties / category / description
      Previous value: -"Preset (gold, coin, coin_retail, currency, currency_government, currency_sana, currency_nima, crypto) or a folder id from tj_list_categories, e.g. '28070'."New value: +"Preset (gold, coin, coin_retail, currency, currency_government, currency_sana, currency_nima, crypto) or a folder id from tj_list_categories."
    • changedInput schema / properties / limit / description
      Previous value: -"Max rows (50 keeps the reply under 15 KB)."New value: +"Max rows."
  2. First observedv0.1.0

TDQS

A4.7/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 behavior the annotations cannot: how units are returned per group (`*_toman` suffix for Rial groups, USD for crypto, a per-row `unit` field when mixed), and that the crypto preset returns roughly 27,000 unordered rows, which is a real performance and ordering caveat an agent needs before calling it.

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?

Four short sentences, front-loaded with the core purpose and the output row shape, then usage triggers, then unit semantics, then the one caveat with its redirect. Nothing is redundant and every sentence carries information an agent would otherwise have to discover by trial.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 compensates by enumerating the returned fields per symbol. Combined with the unit-handling rules and the crypto row-count warning, an agent has everything needed to pick this tool and interpret its response correctly.

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%, so limit and offset are already documented and the baseline is 3. The description still adds meaning beyond the schema by explaining what the `category` presets actually denote in terms of denomination and output shape, which the plain enum list in the schema does not convey.

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?

'Live price table of one TGJU group' names a specific verb-like operation and resource, immediately followed by the exact row shape (price, change, day high/low/open per symbol). It is clearly distinguishable from tj_market_summary and tj_price_history because it is scoped to one category group rather than a market aggregate or a time series.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It gives concrete trigger phrases ('all gold prices', 'all coin prices') and then explicitly excludes the crypto preset, routing the agent to tj_get_prices or tj_search_symbols instead. That is both a when-to-use and a when-not-to-use statement with a named alternative, which is the top of the scale.

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