Skip to main content
Glama

BRAINIAC Exchange Rates

Get timeseries exchange rates

fx_rates_timeseries

Retrieve exchange rates over a date range from the Frankfurter API (ECB data). Returns rates for each working day in the range. Price $0.05 USDC. POST /api/v1/fx/rates/timeseries. Unpaid calls return 402 and do not run.

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "fx_rates_timeseries"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
baseNo
fromYes
symbolsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the cost ($0.05 USDC), the transport (POST /api/v1/fx/rates/timeseries), and the failure mode (unpaid calls return 402 and do not run). It omits rate limiting, auth mechanics beyond payment, and default base-currency behavior, keeping it short of 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.

Conciseness5/5

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

Four short sentences, front-loaded with the purpose, then granularity, price, endpoint, and the payment failure rule. No filler and nothing repeated from structured fields other than a harmless restatement of scope.

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?

Adequate on purpose, cost, and payment behavior, but for a 4-parameter tool with zero schema description coverage and no output schema, it leaves key invocation-relevant details (base currency default, symbols semantics, response shape) undocumented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for 4 parameters, so the description must compensate. It only hints at the 'date range' (from/to); the 'base' and 'symbols' parameters are never explained, and their defaults, uppercase-code format, and single-vs-array behavior for symbols are left entirely to a bare regex pattern.

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 verb and resource ('Retrieve exchange rates over a date range') plus the data source (Frankfurter API / ECB) and return granularity ('each working day'). The date-range scope implicitly separates it from a latest-rates or single-date lookup, but no sibling is named explicitly.

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 'over a date range' phrasing implies when this tool is appropriate, but there is no explicit guidance on choosing it over fx_rates_latest or fx_rates_historical, and no prerequisites beyond the payment note. Usage must be inferred from the scope wording.

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