Skip to main content
Glama

FinanceQuery

Exchange Rate

get_forex
Read-onlyIdempotent

Get a currency pair's current exchange rate, provider-routed (Capability::FOREX).

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_forex"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesQuote currency code (e.g. "EUR")
fromYesBase currency code (e.g. "USD")
fieldsNoComma-separated list of GraphQL field names to include; omitted = all fields

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds only 'provider-routed (Capability::FOREX)', an internal routing tag with little actionable meaning, and says nothing about rate freshness, latency, or failure behavior for an open-world network call.

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 padding. The trailing 'provider-routed (Capability::FOREX)' is internal jargon that contributes little to an agent's decision, slightly reducing value.

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 simple two-required-parameter read tool with full schema coverage and rich annotations, the core is covered. However, with no output schema, the description should hint at what is returned (rate value, timestamp, provider) and does not.

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%, and the schema itself explains base/quote currency codes and the 'fields' projection parameter. The description adds no meaning beyond that, so the baseline 3 applies.

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?

Specific verb ('Get') plus resource ('a currency pair's current exchange rate'), and 'currency pair' naturally separates it from siblings like get_crypto, get_commodity, and get_futures. It does not explicitly name a sibling it replaces, so it falls short of a 5.

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?

There is no when-to-use guidance, no exclusions, and no mention of alternatives such as get_chart for historical series or get_forex_news for context. The word 'current' weakly implies spot-only, but the agent must infer that.

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.