Skip to main content
Glama

BRAINIAC Exchange Rates

Get latest exchange rates

fx_rates_latest

Retrieve latest available exchange rates from the Frankfurter API (ECB data). Rates are delayed reference rates, not real-time market rates. Price $0.01 USDC. POST /api/v1/fx/rates/latest. Unpaid calls return 402 and do not run.

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

Input Schema

NameRequiredDescriptionDefault
baseNo
symbolsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the load well: it discloses data freshness (delayed reference rates, not real-time), cost ($0.01 USDC), transport (POST endpoint), and the failure path (402 without execution). It does not cover rate limits, default base currency, or response shape, which keeps it below 5.

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

Conciseness4/5

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

Four short sentences, front-loaded with the core action and the most decision-relevant caveat (delayed, not real-time). The raw endpoint string is mildly redundant for an agent but not harmful.

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?

Pricing and payment failure are covered, but for a 2-parameter tool with no schema descriptions the definition leaves key calling decisions open: what base defaults to, how symbols filters output, and what the response contains.

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%, so the description must compensate for the two undocumented parameters (base and symbols, both 3-letter currency codes). It says nothing about them – not their meaning, format, defaults, or behavior when omitted.

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 latest available exchange rates, with the data source (Frankfurter/ECB) named. The word 'latest' implicitly separates it from fx_rates_historical and fx_rates_timeseries, 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?

Usage is only implied by 'latest available' – an agent can infer this is for current spot reference rates rather than historical or conversion queries, but there is no explicit when-to-use/when-not guidance or pointer to fx_rates_convert for conversions.

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