Skip to main content
Glama
tgju-mcp

tgju-mcp

by sepehr071

Live prices

tj_get_prices
Read-onlyIdempotent

Retrieve current TGJU symbol quotes with daily change, high, and low; if a live quote is unavailable, get the latest daily close from history.

Instructions

Live price, day change, high and low for one or more TGJU symbols.

Use for current rates. Rial symbols also carry *_toman. stale: true = quote older than 2 days. Slugs missing from the live feed answer with their latest daily close (source: history). Unknown ones go to not_found: use 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": {
      "symbols": "<symbols>"
    },
    "name": "tj_get_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsYesSymbol slugs, e.g. ['price_dollar_rl', 'geram18', 'sekee'].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • changedInput schema / properties / symbols / description
      Previous value: -"Symbol slugs, e.g. ['price_dollar_rl', 'geram18', 'sekee', 'crypto-bitcoin']."New value: +"Symbol slugs, e.g. ['price_dollar_rl', 'geram18', 'sekee']."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive, open-world behavior, and the description still adds substantive runtime semantics: the `stale: true` threshold of 2 days, the `source: history` fallback when a slug is absent from the live feed, and the `*_toman` companion fields for rial symbols. These are non-obvious behaviors an agent could not infer from the annotations or schema.

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 tight sentences, front-loaded with purpose before edge cases. Every sentence carries actionable information — branch behavior, staleness threshold, and fallback routing — with no restatement of the tool name or the schema.

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?

With no output schema, the description carries the return-value burden and does so: it names the returned fields, the stale flag, the source marker, and the not_found outcome. For a single-parameter read tool this leaves nothing an agent needs missing.

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 description coverage is 100% and already documents the symbols array with examples, so the baseline is a 3. The description adds genuine meaning on top: slugs may resolve to a stale quote, a historical close, or not_found, and rial slugs yield additional `*_toman` keys — information that changes how an agent interprets a given symbol value.

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?

States a specific resource and the exact fields returned: 'Live price, day change, high and low for one or more TGJU symbols.' The scope ('one or more', batch) and the live-vs-historical framing let an agent separate it from tj_price_history and tj_search_symbols without opening any 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?

'Use for current rates' gives the positive selection condition, and the not_found branch explicitly routes the agent to tj_search_symbols. It stops short of naming tj_price_history as the alternative for past data, so the exclusion is implied by 'current rates' rather than stated.

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