Skip to main content
Glama

indonesia_series

Read-only

Paid $0.25 per call: daily exchange-rate history longer than the 30 days /fx carries, up to 365 prints in one call. Deeper than that is licence-only — 365 prints/call on pilot, 1,825 on growth and 3,650 on enterprise ($700, 90 days), the two deepest also taking the whole series as one ?format=csv|jsonl file.

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_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoQuote currency, ISO 4217. Default IDR (rupiah).
daysNoDaily points wanted, 1-365 without a licence and up to 3,650 on an enterprise licence. A request past this caller's ceiling is refused before any payment.
fromNoBase currency, ISO 4217. Default USD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior5/5

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

With only readOnlyHint supplied, the description carries real behavioral weight: it discloses the per-call price ($0.25), the tier ceilings (365/1,825/3,650 prints), the licence requirement and cost ($700, 90 days) beyond the free range, and that an over-ceiling request is refused before payment. It also reveals that the two deepest tiers can return the entire series as a single csv/jsonl file, which an agent cannot infer from any structured field.

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?

Two sentences with no wasted glue, but the opening leads with price rather than purpose, making the agent read past pricing before learning what the tool returns. The tier ladder (365 / 1,825 / 3,650) repeats the ceiling already stated in the days parameter and is the bulkiest part of the text.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter read tool with no output schema and a readOnly annotation, the definition covers cost, limits, licensing and export formats well, but it never describes the shape of a returned 'print' (fields, timestamp granularity, ordering) despite there being no output schema to lean on. The undefined 'prints' terminology leaves a gap an agent must guess at.

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 from/to/days semantics and defaults are already documented and the description does not need to restate them. It adds the notion of 'prints' as the unit counted against a ceiling, but leaves that term undefined and mentions a ?format=csv|jsonl option that is not even present in the input schema, which muddies rather than clarifies the parameters.

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?

The description clearly identifies the resource as daily exchange-rate history and contrasts its depth with the sibling endpoint it names as /fx (the 30-day tool), so an agent can tell the two apart. It never uses a clean verb like 'returns', and it does not distinguish itself from indonesia_series_preview, but the scope statement ('up to 365 prints in one call') is specific enough to route correctly.

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?

Usage is implied with reasonable precision: pick this tool when you need history longer than the 30 days /fx carries, and go elsewhere if you need more than 365 points without a licence. The alternatives are named by contrast rather than listed explicitly, and the sibling preview tool is never mentioned, which keeps it short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources