Skip to main content
Glama

Nivel del río hoy

nivel_del_rio
Read-only

Devuelve la última altura publicada por la Dirección de Meteorología e Hidrología de Paraguay en la estación de cada zona (o de una zona), con la variación del día, la de los últimos 7 días y la fecha de cada lectura. Una estación sin lectura reciente sale marcada, sin cifra de hoy.

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_del_rio"
  }
}

Input Schema

NameRequiredDescriptionDefault
zonaNoZona de pesca: id (pilar, pasodepatria, cerrito, ayolas, ciudaddeste, encarnacion, villaflorida, villeta, asuncion, concepcion, vallemi, bahianegra) o nombre.
idiomaNoIdioma de la respuesta: es (por defecto), en o pt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond that: the upstream data source, that variations for the day and the last 7 days accompany each reading, and the edge case that a station lacking a recent reading is returned flagged with no current figure rather than being omitted.

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 tightly packed sentences with no filler: the first front-loads what is returned and from where, the second handles the degraded-data case. Every clause carries information an agent needs.

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?

With no output schema, the description compensates by enumerating the payload (current height, day variation, 7-day variation, reading date, flagged stations). For a read-only, zero-required-parameter lookup this leaves nothing essential unexplained.

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 schema already documents both parameters and their enum/values. The description still adds meaning by clarifying that the zona parameter is optional and that omitting it yields one entry per zone, a default behavior the schema does not state.

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 concrete verb and resource (returns the latest river height per station) and names the data source, the Dirección de Meteorología e Hidrología de Paraguay, so the agent knows exactly what is being fetched. It does not explicitly differentiate itself from siblings, but the content is specific enough to be unambiguous.

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 implies when the tool applies (checking current river level for one or all fishing zones), and the phrase 'de cada zona (o de una zona)' hints that omitting the zone is valid. It gives no explicit when-to-use vs. when-not-to-use guidance and never points to an alternative such as listar_zonas for zone discovery.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources