convertConvert an amount between currencies using the best available Uruguayan market rates. Foreign↔foreign routes through UYU (Uruguayan peso). Codes: USD, EUR, ARS, BRL, UYU, etc.
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | Target ISO code, e.g. UYU | |
| from | Yes | Source ISO code, e.g. USD | |
| amount | Yes | Amount to convert |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses a key non-obvious behavior: foreign-to-foreign conversions route through UYU. It also reveals that rates come from the Uruguayan market, which is important context beyond the schema.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with no wasted words. The primary purpose is front-loaded, the important routing caveat is stated second, and the supported-codes list is compact.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple three-parameter conversion tool with no output schema, this description covers purpose, rate source, routing behavior, and supported codes. It does not describe the response shape, but the operation is straightforward enough that the missing output details are a minor gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already documents amount, from, and to at 100% coverage, so the baseline is 3. The description adds value by listing supported currency codes and the routing-through-UYU behavior, which clarifies what from/to values mean in practice.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: convert an amount between currencies. It also adds a distinctive scope—best available Uruguayan market rates—and clarifies routing behavior, which makes it easy to tell apart from siblings like get_rates.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description clearly implies this is the tool for currency conversion, but it does not explicitly say when to prefer it over related siblings such as get_rates. There is useful context about rate sourcing, but no direct alternative guidance or exclusion criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools cover clearly distinct tasks: conversion, historical data, news, summaries, and house listings. However, best_house overlaps with get_rates since get_rates already identifies the best buy/sell house, though best_house's narrower focus helps reduce ambiguity.
The tool names generally follow a readable snake_case style, with many using a get_* prefix for data retrieval. A few names like best_house, convert, and daily_summary deviate from that pattern, but the naming remains predictable and easy to understand.
Seven tools is a well-scoped size for a specialized Uruguayan exchange-rate server. Each tool contributes a distinct capability without unnecessary redundancy or bloat.
The surface covers the core domain well: current rates, best house selection, currency conversion, historical evolution, house listings, news, and AI-generated summaries. There are no obvious dead ends or missing operations for the server's stated purpose.