Skip to main content
Glama

Nivel y caudal del río Uruguay en las escalas de Prefectura (INA)

nivel_rio_ina
Read-onlyIdempotent

Fetch Uruguay River water level or flow data from INA for Concordia and Salto Grande scales over a selected date range, including alert, evacuation, and low-water levels.

Instructions

Altura (H, en metros) o caudal (Q, en m³/s) del río Uruguay en las escalas de Prefectura Naval Argentina que publica el sistema de alerta del INA: Concordia (frente a Salto, desde 1931) y Salto Grande Arriba y Abajo (la represa). Con los niveles de alerta, evacuación y aguas bajas de la escala.

desde/hasta AAAA-MM-DD, por defecto los últimos 30 días. Hasta 400 días devuelve un punto por día; más largo, uno por mes (la serie entera cabe en un pedido). Leer dias_de_atraso antes de decir "hoy": el caudal de Concordia viene con meses de atraso en la fuente, y el dato del día se carga por la tarde. Para la estación Salto de la CTM y el río comparado con otros años, usar nivel_rio y nivel_rio_comparado.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nivel_rio_ina"
  }
}

Input Schema

NameRequiredDescriptionDefault
desdeNo
hastaNo
escalaNoConcordia
variableNoH

Output Schema

NameRequiredDescriptionDefault
notaYes
avisoNo
bajadoYes
escalaYes
fuenteYes
puntosYes
unidadYes
nivelesYes
serie_idYes
variableYes
agregacionYes
ultima_cargaYes
copia_vencidaNo
dias_de_atrasoYes
ultima_lecturaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.14.0

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare a safe, idempotent, read-only open-world read, so the baseline bar is lower. The description nevertheless adds genuinely useful behavior: default 30-day window, daily granularity up to 400 days then monthly, and source latency (Concordia flow lags months; the current day's value loads in the afternoon). It does not cover pagination or output shape, but the output schema exists.

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?

Dense but front-loaded: identity of the series first, then date semantics, then resolution behaviour, then the latency caveat and alternatives. Every sentence carries information, though the long parenthetical opening and packed clauses make it heavier than necessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described; the description instead supplies what structured fields cannot — resolution changes, latency, and the pre-condition of checking dias_de_atraso. Combined with the sibling routing, an agent has everything needed to call it correctly.

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?

With 0% schema coverage the description must carry the parameters, and it does most of it: desde/hasta format (AAAA-MM-DD) and default window, variable H vs Q with units, and the station names that make up the escala enum. The only omission is that the defaults for escala (Concordia) and variable (H) are left to the schema's default fields rather than restated.

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?

Names the specific quantity (H in metres or Q in m³/s), the river, the source system (INA alert system), and the exact stations (Concordia, Salto Grande Arriba/Abajo), plus the alert/evacuation/low-water thresholds bundled in. It explicitly contrasts itself with nivel_rio and nivel_rio_comparado, so an agent can pick the right tool without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States the selecting condition for the alternatives: for the CTM Salto station or year-over-year comparison use nivel_rio / nivel_rio_comparado. It also gives an operational rule — read dias_de_atraso before claiming 'hoy' — which prevents a concrete misuse.

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