get_latest_gold_ratesReturns latest Arzbin gold and coin rates in Toman. Data is indicative market data, not financial advice.
| Name | Required | Description | Default |
|---|---|---|---|
| types | No | Optional gold or coin codes such as EMAMI, AZADI, GOLD_GRAM. Omit for all available gold rates. |
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | ||
| source | Yes | ||
| disclaimer | Yes | ||
| generatedAtUtc | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description carries a lower burden. It adds context by noting the data is indicative market data and not financial advice, which helps the agent set appropriate expectations. No contradictions with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, with the main purpose in the first sentence and a disclaimer in the second. No wasted words, and the most important information is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple with one optional parameter and an output schema, and annotations cover safety. The description plus schema provides sufficient context for correct selection and invocation. No critical information is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema fully describes the 'types' parameter with examples and default behavior (omit for all), achieving 100% schema coverage. The description adds no additional parameter details, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns latest Arzbin gold and coin rates in Toman, using a specific verb and resource. It also distinguishes from sibling tools like get_latest_crypto_rates and get_latest_fiat_rates by focusing on gold and coin rates.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no explicit guidance on when to use this tool vs alternatives, but the name and description imply it is for gold/coin rates. It does not mention exclusions or when to prefer sibling tools, so usage guidance is implied rather than explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct aspect of the market data domain: converting amounts, fetching current rates for different asset classes, retrieving historical data, and accessing rate sources. The clear differentiation between crypto, fiat, gold, and conversion prevents ambiguity.
All tools follow a consistent get_/convert_ verb-noun snake_case pattern. The only deviation is convert_to_toman, which still fits the verb_object style and is distinguishable from the get_ family.
With 6 tools, the server is well-scoped for its purpose of providing Toman-denominated market data. Each tool covers a necessary function—rates for various asset classes, conversion, history, and source info—without unnecessary bloat.
The tool surface comprehensively covers the domain: current rates for crypto, fiat, and gold, conversion to Toman, historical OHLC data, and source comparison. No obvious gaps exist for a market data server focused on Iranian exchange rates.