Skip to main content
Glama
Sign In

Cambio Uruguay

by io.github.eduair94
OverviewDiscussionsAdmin

Best exchange house

best_house
Read-onlyIdempotent

The single best casa de cambio right now to buy or sell a currency. side='buy' means you buy the currency (best = lowest sell price); side='sell' means you sell it (best = highest buy price).

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>",
      "side": "<side>"
    },
    "name": "best_house"
  }
}

Input Schema

NameRequiredDescriptionDefault
sideYes'buy' = you buy the currency; 'sell' = you sell it
currencyYesISO currency code, e.g. USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), so the description's job is to explain semantics — and it does the important part: defining what 'best' means per side (lowest sell price vs highest buy price), which is genuinely non-obvious. It does not say whether results are cached, how fresh 'right now' actually is, or what permissions/coverage limits exist.

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 the core purpose, then the price-direction rule. No filler, and the parentheticals earn their place by disambiguating 'best'.

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?

With no output schema, the description never says what is actually returned — just one exchange house name, its rate, an address, a spread? For a 'best X' tool the return shape matters for downstream use. Annotations and the 100%-covered schema keep it serviceable, but the omission leaves a real gap.

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 both parameters are documented in-schema, so baseline is 3. The description mirrors the side enum definition almost verbatim and adds no guidance on currency code variants or how side interacts with the returned rate beyond the price-direction mapping.

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 resource and outcome: 'the single best casa de cambio right now' for buying or selling a currency. The superlative 'single best' clearly distinguishes it from aggregate/lookup siblings like get_rates or convert, though it never names those siblings explicitly.

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?

'right now' implies this is a point-in-time recommendation rather than a historical or full-list lookup, which implicitly routes the agent away from get_rates/list_houses. However, no explicit when-to-use/when-not or named alternative is given, so the agent must infer that this returns one winner versus a full table.

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