Skip to main content
Glama
Sign In

Cambio Uruguay

by io.github.eduair94
OverviewDiscussionsAdmin

Convert an amount

convert
Read-onlyIdempotent

Convert 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.

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

Input Schema

NameRequiredDescriptionDefault
toYesTarget ISO code, e.g. UYU
fromYesSource ISO code, e.g. USD
amountYesAmount to convert

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/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 genuinely new behavioral context: rates are the 'best available' Uruguayan market rates and foreign↔foreign conversions are triangulated through UYU — a non-obvious mechanic the agent would otherwise have to guess. It stops short of disclosing rate freshness, rounding, or fees.

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?

Two compact sentences, zero filler. The core action is front-loaded and the triangulation rule follows as supporting detail.

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?

There is no output schema, so the description should say what comes back — the converted amount, the rate applied, a timestamp, or a triangulated pair. That return-shape gap, plus no note on rate staleness or error behavior for invalid codes, leaves it only minimally complete for a conversion tool.

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%, so the baseline is 3, and the description earns an extra point by enumerating valid currency codes (USD, EUR, ARS, BRL, UYU, etc.), which matters because the schema defines no enums for from/to. It still does not clarify whether codes are case-sensitive or how unsupported codes fail.

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 (convert an amount between currencies) and scopes the data source to Uruguayan market rates. It implicitly separates itself from the rate-listing sibling get_rates, but never names it, so sibling differentiation is left to inference.

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 makes the use case clear (converting an amount), but gives no explicit when-to-use vs. when-not guidance and does not route the agent to get_rates for raw rate retrieval or to any other sibling. Usage is implied rather than stated.

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

All Cambio Uruguay 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