agentweb-mcp

currency_convert

Convert between 30+ currencies using live ECB exchange rates. Returns converted amount and exchange rate.

Instructions

Convert between currencies using live ECB exchange rates. Supports 30+ currencies (USD, EUR, GBP, JPY, etc.). Returns converted amount and exchange rate. ~0.5s.

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": {
      "amount": "<amount>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "currency_convert"
  }
}

Input Schema

Name	Required	Description
`amount`	Yes	Amount to convert
`from`	Yes	Source currency code (e.g. 'USD', 'EUR', 'GBP')
`to`	Yes	Target currency code (e.g. 'EUR', 'JPY', 'GBP')

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.17.0Jun 21, 2026

TDQS

A4.5/5.0

Behavior4/5

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

No annotations are provided, so the description must bear the full burden. It discloses the data source (ECB), scope (30+ currencies), returned items (converted amount, exchange rate), and performance (~0.5s latency). This provides sufficient behavioral transparency for a simple conversion tool.

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?

Three short sentences packed with essential information. No fluff, each sentence earns its place. Front-loaded with the main action 'Convert between currencies'.

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

Completeness5/5

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

For a simple conversion tool with 3 required parameters and no output schema, the description is complete. It covers purpose, input parameters (implicitly), output format, data source, and latency. No gaps.

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% with basic descriptions. The description adds value by mentioning 'live ECB exchange rates' and examples like 'USD, EUR, GBP, JPY', which enriches the parameter semantics beyond the schema's minimal descriptions.

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 verb 'Convert', the resource 'currencies', and distinctive features like 'live ECB exchange rates', '30+ currencies', and output details. It differentiates from sibling tools which are unrelated to currency conversion.

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?

The description does not explicitly state when to use or not use this tool, but given the sibling tools are mostly travel/agent related, it is inherently clear that this tool is for currency conversion. No exclusion or alternative guidance is provided, but context suffices.

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