mcp-Uruguay

Promedio mensual de una cotización del BCU

cotizacion_mensual

Read-onlyIdempotent

Calculate monthly average BCU exchange rates for USD, UI, ARS or BRL between two YYYY-MM months (up to 240), returning published days per month and flagging the current month as incomplete.

Instructions

Promedio mensual de una cotización del BCU entre dos meses AAAA-MM (hasta 240 meses), con la cantidad de días publicados de cada mes. El mes en curso viene marcado como incompleto.

Input Schema

Name	Required	Description	Default
`desde`	Yes
`hasta`	Yes
`moneda`	Yes

Output Schema

Name	Required	Description	Default
`nota`	Yes
`meses`	Yes
`bajado`	Yes
`fuente`	Yes
`moneda`	Yes
`nombre_bcu`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.13.2Oct 24, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower; the description nonetheless adds real behavioral facts: a hard 240-month cap, per-month published-day counts, and the current month being flagged as incomplete. It does not discuss rate limits or error behavior on out-of-range dates.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, zero filler, and the core operation is front-loaded before the qualifiers about day counts and incomplete months. Slightly dense as a single run-on sentence but efficient.

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?

For a three-parameter, read-only aggregation tool with an output schema already defining return shape, the description covers scope, limits, and the notable 'incomplete current month' caveat. The only residual gap is the currency parameter's semantics.

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 description coverage is 0%, so the description must carry parameter meaning; it does clarify the AAAA-MM month format and that 'desde'/'hasta' are the two bounds, which is genuinely additive. However, it says nothing about 'moneda' beyond what the enum values convey, so compensation is partial.

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: monthly average of a BCU quote between two months, with published-day counts. This clearly separates it from the daily quote sibling 'cotizacion', though the description never names that sibling 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?

The phrase 'Promedio mensual ... entre dos meses' implies this is the multi-month aggregation tool rather than a single-quote lookup, but there is no explicit when-to-use/when-not guidance or reference to alternatives such as 'cotizacion'.

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