Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_geo_live_fx_rates

Fetch live FX rates for a base currency and convert an amount into specified target currencies, enabling current currency data retrieval and quick conversion calculations.

Instructions

[Global Locale] Live currency (FX) rates for a base currency with optional amount conversion Measured p50 12 ms, p95 14 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://geo.caelaralabs.com.

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": "caelara_geo_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 observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does add some operational context: "Live" implies real-time rates, and it discloses measured latency (p50 12 ms, p95 14 ms) plus the upstream endpoint. It still omits whether rates are cached, what the data source is, whether it is safe to call repeatedly, and what the response contains.

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?

The purpose is front-loaded in one compact sentence with no filler. The trailing benchmark and endpoint clauses are terse, although the precise latency numbers and dated benchmark citation occupy space without helping an agent decide how or when to call the tool.

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 tool with no output schema, the description should explain the return shape (a rates map, a converted amount, or both), and it does not. Safety and mutability are obvious from the purpose, so the remaining gap is mainly the response shape and error behavior.

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 description coverage is 100%, so the schema already explains all three parameters and their defaults, and the baseline is a 3. The description only reinforces that the base currency is required and the amount conversion is optional, without adding format or behavior details beyond the schema (e.g., how symbol lists are matched or normalized).

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 verb and resource: "Live currency (FX) rates for a base currency with optional amount conversion." An agent can tell this is a read-only FX lookup rather than VAT/GST lookup or a checkout composite. The only noise is the bracketed "[Global Locale]" prefix, which adds no disambiguation against siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description never says when to use this tool versus the sibling tools (e.g., vat_gst_rate_lookup or cross_border_checkout_composite), nor does it state prerequisites, expected rate freshness, or what happens when a currency is unsupported. Usage is only implied by the tool's purpose.

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

Deploy Server

Other Tools