Arzbin MCP Server

Get latest fiat rates

get_latest_fiat_rates

Read-onlyIdempotent

Returns latest Arzbin fiat currency rates in Toman. Data is indicative market data, not financial advice.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_latest_fiat_rates"
  }
}

Input Schema

Name	Required	Description	Default
`codes`	No	Optional fiat currency codes such as USD, EUR, AED, GBP. Omit for all available fiat rates.

Output Schema

Name	Required	Description	Default
`data`	Yes
`source`	Yes
`disclaimer`	Yes
`generatedAtUtc`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 28, 2026

TDQS

A4/5.0

Behavior4/5

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

The description adds a data quality caveat ('indicative market data, not financial advice') beyond the annotations, providing useful context about data reliability. It does not disclose rate limits or error behavior, but annotations already cover the read-only and idempotent safety profile.

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, no fluff, front-loads the key function and then a caveat. Every word earns its place.

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?

The tool is simple with one optional parameter and an output schema. The description adequately covers purpose and data quality; the schema handles filtering details. It only lacks explicit usage alternatives, already accounted for in the usage dimension.

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 coverage is 100% for the single parameter (codes), including examples and default behavior. The description does not add parameter semantics, but the baseline of 3 is appropriate when the schema fully documents the parameters.

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?

The description clearly states the tool returns the latest fiat currency rates in Toman, with a specific resource (Arzbin fiat rates) and scope (latest, in Toman). It distinguishes from siblings like crypto/gold rates and market history by explicitly focusing on fiat currency.

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?

The description does not explicitly mention alternatives or exclusions, such as when to use convert_to_toman or get_market_history. Usage is implied from the tool name and mention of 'fiat rates,' but lacks clear guidance on when not to use this tool.

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

All Arzbin MCP Server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.