Skip to main content
Glama

Calidad del agua potable de OSE por localidad

calidad_agua
Read-onlyIdempotent

Query OSE drinking-water laboratory results by locality and quarter since 2017, including coliforms, E. coli, pH, turbidity, color, and odor, with sample counts and parameter ranges.

Instructions

Los análisis de laboratorio con que OSE controla el agua potable, por localidad y trimestre, desde 2017: coliformes totales y Escherichia coli (presencia o ausencia), pH, turbidez (NTU), color verdadero (UC) y olor.

Sin localidad, la lista de localidades con su departamento. Con localidad, cada trimestre con la cantidad de muestras y, por parámetro, cuántos análisis fueron mediciones y cuántos límites de detección (<5), con el mínimo y el máximo de las mediciones. parametro filtra uno (por ejemplo turbidez); desde/hasta son AAAA o AAAA-Tn (por ejemplo 2024-T3). No dice si el agua cumple la norma: informa lo que OSE publicó. La primera consulta baja unos 122 MB y tarda.

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": "calidad_agua"
  }
}

Input Schema

NameRequiredDescriptionDefault
desdeNo
hastaNo
localidadNo
parametroNo

Output Schema

NameRequiredDescriptionDefault
notaNo
avisoNo
bajadoNo
fuenteNo
localidadNo
trimestresNo
localidadesNo
departamentoNo
copia_vencidaNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.14.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world, but the description adds what they cannot: the first query downloads ~122 MB and is slow, and the tool reports published data without judging regulatory compliance. It also discloses the return shape (sample counts, measurement vs detection-limit counts, min/max).

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?

Front-loaded with the resource and scope, then the two result modes, then parameter syntax, then caveats. Dense but every sentence carries information; the only cost is that the parameter syntax and caveats are packed into a single long paragraph.

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?

For a four-parameter, zero-required, read-only query tool with an output schema, the description covers result modes, parameter formats, data caveats, and the large first-call cost. Nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry the load and it does: `localidad` toggles between two result modes, `parametro` filters a single parameter with an example (`turbidez`), and `desde`/`hasta` accept AAAA or AAAA-Tn with an example (2024-T3). All four parameters gain meaning beyond the bare schema.

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?

States a specific verb and resource: OSE's laboratory analyses of drinking water, broken down by locality and quarter since 2017, and enumerates the measured parameters (coliforms, E. coli, pH, turbidity, true color, odor). An agent can tell exactly what data this returns and that it is unrelated to the sibling tools listed.

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

Usage Guidelines4/5

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

Gives clear conditional usage: without `localidad` you get the locality list with department, with `localidad` you get per-quarter detail. It also sets scope expectations explicitly ('No dice si el agua cumple la norma: informa lo que OSE publicó'). It does not name alternative tools, but no sibling appears to overlap, so the gap is minor.

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