Skip to main content
Glama
Sign In

Cambio Uruguay

by io.github.eduair94
OverviewDiscussionsAdmin

Get exchange rates

get_rates
Read-onlyIdempotent

Current buy/sell rates for a currency across Uruguayan exchange houses (casas de cambio): market average, best buy/sell house, lowest spread, and the full per-house list. Excludes BCU and interbank quotes. Currency is an ISO code like USD, EUR, ARS, BRL.

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": {
      "currency": "<currency>"
    },
    "name": "get_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
currencyYesISO currency code, e.g. USD, EUR, ARS, BRL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, so safety is covered. The description usefully adds that values are 'current' snapshots from casas de cambio with a defined source boundary, but says nothing about freshness/latency, number of houses covered, or how 'market average' is computed.

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 sentences, front-loaded with what is returned, then the exclusion, then the parameter example. Every clause carries information and nothing is padded.

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?

There is no output schema, and the description compensates well by listing the four returned elements (market average, best buy/sell house, lowest spread, per-house list). Minor gap: it doesn't indicate coverage breadth (how many houses) or what an empty/unknown currency yields.

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 coverage is 100% and the single parameter already documents ISO codes with examples, so the description's 'ISO code like USD, EUR, ARS, BRL' is a near-verbatim repeat. No added syntax, case-handling, or invalid-code behavior is provided, so the baseline 3 applies.

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 names a specific verb+resource ('current buy/sell rates for a currency'), states the geographic/institutional scope (Uruguayan exchange houses / casas de cambio), and enumerates what is returned. It also carves out a boundary ('excludes BCU and interbank quotes') that separates it from a general rates source.

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 exclusion of BCU and interbank quotes implicitly scopes usage, but the description never says when to prefer this over siblings like 'convert' (conversion) or 'best_house' (best-house lookup), even though the returned fields overlap with best_house. Usage is inferable 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