Skip to main content
Glama

Caelara Labs Global Locale

live_fx_rates

Live foreign-exchange rates for a base currency with optional amount conversion

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

Input Schema

NameRequiredDescriptionDefault
baseNoBase currency ISO 4217 (default USD)
amountNoAmount of the base currency to convert
symbolsNoComma list of target currencies (default major set)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden and does little beyond the word "live," which hints at freshness/real-time data. It says nothing about rate source, caching/refresh behavior, whether rates are indicative or tradable, or any auth or rate-limit constraints.

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?

A single front-loaded sentence with no redundant wording; the core resource is stated first and the modifier follows. It is efficient, though its brevity borders on under-specification for a tool with no annotations.

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

Completeness2/5

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

For a tool with zero annotations, zero required parameters, and no output schema, the description should say more about what comes back (rate values, converted amounts, base/symbol echo) and how defaults behave. As written, an agent cannot predict the response shape or the semantics of the amount conversion without calling it.

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 the schema already documents base, amount, and symbols with defaults, making 3 the baseline. The description adds only marginal meaning: it clarifies that amount triggers a conversion and that base/amount work together, but gives no format, rounding, or cross-rate behavior for conversion.

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 names a specific resource (live foreign-exchange rates) and its scope (a base currency, with optional amount conversion), which is clearly distinct from siblings like vat_gst_rate_lookup or country_iso_enricher. It stops short of explicitly contrasting with any alternative, so it is clear but not sibling-differentiated.

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?

"Live" implies current rather than historical rates, which gives the agent an implicit usage signal, and "optional amount conversion" hints at the two modes of use. There is no explicit when-to-use guidance, no prerequisites, and no statement of when this tool is the wrong choice versus something else.

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