Skip to main content
Glama

forex.mobile broker data

Exchange rate

get_rate
Read-only

Reference exchange rate between two currencies (fiat from ExchangeRate-API, refreshed by the provider about once a day; BTC/ETH from CoinGecko against USD, EUR or GBP). Not a dealing price or a broker quote. Returns an error rather than a guess when the rate is unavailable.

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

Input Schema

NameRequiredDescriptionDefault
toYesQuote currency code, e.g. AED
fromYesBase currency code, e.g. USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, non-destructive, openWorld), and the description adds genuinely new context: the upstream data sources, an approximately daily refresh cadence that explains staleness, and a hard failure mode ('returns an error rather than a guess') for missing rates. The non-idempotent hint is consistent with a rate that can change between calls.

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?

Two sentences, front-loaded with what the tool returns, followed by the exclusion and the failure behavior. No filler and nothing buried.

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

Completeness4/5

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

For a two-parameter read-only lookup with no output schema, the definition covers sourcing, freshness and error semantics well. It leaves the success payload shape (single rate value vs. timestamped object) unstated, which matters slightly given there is no output schema to fall back on.

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

Parameters4/5

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

Schema coverage is 100% so the two currency codes are documented, and the description still adds meaning by constraining crypto quotes to USD, EUR or GBP while leaving fiat open. It does not clarify case sensitivity or whether symbols vs ISO codes are accepted, so it is above baseline but not exhaustive.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a precise verb+resource — a reference exchange rate between two currencies — and immediately bounds the scope by naming the source per asset class (ExchangeRate-API for fiat, CoinGecko for BTC/ETH). The line 'Not a dealing price or a broker quote' cleanly separates it from the sibling broker tools.

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?

Gives a clear when-not ('not a dealing price or a broker quote'), which tells an agent not to use it for pricing a trade. It stops short of naming which sibling to use instead for broker quotes, so it falls just short of full routing guidance.

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