news

indonesia_fx

Read-only

Paid $0.05 per call: FX rates for any pair the ECB publishes — EUR/USD, GBP/JPY, USD/IDR — latest reference rate plus a 30-day daily series and percentage change. Defaults to USD→IDR. Source: Frankfurter (ECB/BoE reference rates).

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": "indonesia_fx"
  }
}

Input Schema

Name	Required	Description
`to`	No	Quote currency, ISO 4217. Default IDR.
`days`	No	Length of the daily series, 1-30. Anything longer is a different route: /series.
`from`	No	Base currency, ISO 4217. Default USD.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026

changedInput schema / properties / days / description

Previous value: -"Length of the daily series, 1-365. Default 30."New value: +"Length of the daily series, 1-30. Anything longer is a different route: /series."

AddedNov 1, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations only declare readOnlyHint, so the description carries the rest: per-call pricing ($0.05), upstream source (Frankfurter, ECB/BoE reference rates), and the composition of the response. Cost and data provenance are exactly the kind of behavior an agent cannot infer from annotations. No pagination or failure-mode detail, hence not a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense sentence plus a source clause, with cost front-loaded — efficient overall. It packs four separate facts (price, scope, returns, source) into a single sentence, which reduces scannability slightly.

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?

For a read-only, three-optional-parameter tool with no output schema, the description covers inputs-by-default, output shape, data source, and cost. Only the relationship to the overlapping convert_currency sibling is unaddressed.

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%, so defaults and the 1-30 range are already documented; the description only restates the USD→IDR default and rate source. It does not explain currency-code formatting or behavior for unsupported pairs, so it adds little beyond the schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (FX rates from ECB/Frankfurter) plus exactly what is returned: latest reference rate, 30-day daily series, and percentage change. It also clarifies the tool is not Indonesia-only despite the name ('any pair the ECB publishes'), which is useful. It stops short of distinguishing itself from the sibling convert_currency, so it is not a 5.

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?

Gives a clear default (USD→IDR) and an implicit boundary: `days` caps at 30, longer ranges belong to a '/series' route, matching the schema note. There is no explicit when-to-use-versus-convert_currency guidance, which is the main gap.

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

All news 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.

Resources

Need Help?