Skip to main content
Glama
Sign In

Toolcall

by click.toolcall
OverviewDiscussionsAdmin

fx-rates

Foreign exchange reference rates from the European Central Bank. Base currency plus optional symbols filter. Updated daily on ECB schedule. JSON response. [Paid: $0.002 USDC per call via x402 on Base; the calling client pays automatically.]

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": "fx-rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseNoBase currency code, default USD
symbolsNoComma-separated target currency codes, optional

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description effectively discloses the daily update schedule, JSON response format, and cost per call. This adds value beyond standard expectations.

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?

The description is two sentences long, each sentence adding critical information: function and key parameters, then cost and payment mechanism. No wasted words.

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 simple data retrieval tool with no output schema, the description covers the essential aspects: data source, update frequency, filtering, and cost. Minor omission of error handling is acceptable given its simplicity.

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 includes clear parameter descriptions. The tool description echoes the schema without adding new semantic meaning, so baseline score is appropriate.

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?

The description clearly states the tool provides foreign exchange reference rates from the European Central Bank, and distinguishes itself from sibling tools like crypto-spot by specifying the data source and commercial nature.

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?

The description explains what the tool does but does not provide explicit guidance on when to use it over alternative financial tools. Context signals show many siblings, making such guidance beneficial.

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

All Toolcall toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources