Skip to main content
Glama
openapi-mcp-sdk

openapi-mcp-sdk

Get Today Exchange Rates

get_today_exchange_rates

Retrieve today's world exchange rates based on USD value to convert currencies and compare international rates.

Instructions

Obtain daily world exchange rates based on USD value.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the entire disclosure burden, and it omits the important traits: whether data is cached or live, the source/provider, whether an API key or subscription is required, and what the response looks like. It only discloses that rates are daily and USD-based.

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?

A single short sentence with no filler, and the key scoping detail (daily, USD-based) is front-loaded. Nothing is wasted or buried.

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 zero-argument tool with no output schema and no annotations, the description should describe the returned data shape (e.g., a map of currency codes to rates) and coverage of currencies. It states only the base currency, so an agent still cannot anticipate the response payload.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The mention of USD as the base currency is a small useful note even though no parameter governs it.

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 ('Obtain daily world exchange rates') plus the base currency (USD), which is concrete enough to know what data comes back. It does not differentiate from siblings, though none of the listed siblings are exchange-rate tools, so confusion risk is low.

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 mention of prerequisites or alternatives, and no indication of how 'today' is determined (timezone, refresh cadence) or what to do if today's rates are unavailable. 'Daily' hints at cadence but is the only usage-adjacent signal.

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