Skip to main content
Glama
xmpuspus

ph-civic-data-mcp

by xmpuspus

River flood forecast for a Philippine location

get_flood_forecast
Read-onlyIdempotent

Retrieve daily river discharge forecasts for Philippine places to evaluate flood risk. Outputs discharge rates and bounds in cubic meters per second for specified forecast periods.

Instructions

Daily river discharge forecast for a Philippine place, from Open-Meteo's GloFAS model.

Returns a daily river_discharge_m3s series for the nearest river cell to the resolved location, plus its max and min bounds, in cubic meters per second. This is a model estimate, not a gauge reading, so treat it as one signal among many for flood risk. Examples:

get_flood_forecast("Cagayan de Oro") # 7-day default forecast get_flood_forecast("Marikina", forecast_days=14, past_days=3) # 14 days ahead, 3 days back

On failure: an unresolved location, or a forecast_days or past_days value that is not a whole number or is out of range, returns data_status "invalid_request", with validation_error true and days []. A PSGC outage during location resolution, or an Open-Meteo fetch failure, returns data_status "unavailable", with upstream_error true and days []. A response with no readable daily.time entries, or a river_discharge list shorter than daily.time (including an empty list), returns data_status "indeterminate", with upstream_error true, days [], and is never cached.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locationYesCity, municipality, or province name.
past_daysNoDays of past discharge to include, from 0 to 30. Default 0.
forecast_daysNoDays ahead to forecast, from 1 to 30. Default 7.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.8.0

TDQS

A4.8/5.0
Behavior5/5

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

The description thoroughly discloses behavior beyond the annotations: it states the output is a model estimate rather than a gauge reading, and enumerates three distinct failure modes (invalid_request, unavailable, indeterminate) with exact conditions and returned fields. No contradiction with the readOnly/idempotent hints.

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?

The description is detailed but efficiently organized, with a clear opening statement, examples, and a structured failure mode list. Slightly longer than necessary but every sentence adds critical operational detail.

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?

The presence of an output schema is noted, and the description provides a high-level summary of the response (daily series, max/min bounds, units). It does not repeat the schema verbatim but gives enough context for an agent to understand the result shape and error handling.

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?

All three parameters are fully described in the input schema, and the description repeats their semantics (e.g., location is a city/municipality/province, past_days range 0-30, forecast_days range 1-30). The description also illustrates their usage in the examples.

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?

The description clearly states it provides a daily river discharge forecast for a Philippine location from the GloFAS model, specifying the return series and units. It distinguishes itself from other weather and disaster tools by focusing on river discharge.

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?

Provides explicit usage context with examples for both default and customized parameters, and explicitly advises treating the output as 'one signal among many' for flood risk. This guides an agent on when and how to invoke the tool.

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