ph-civic-data-mcp

Overview Schema Source Related Servers Discussions Admin

PAGASA public advisory, bulletin, and storm surge files

list_pagasa_advisory_files

Read-onlyIdempotent

List PAGASA advisory PDF files (weather, cyclone, storm surge) from public directories, newest first, with optional kind filter and count limit. Returns file metadata like URL, last modified, and size.

Instructions

List PAGASA public PDF files from a pubfiles directory listing, newest first.

Reads the nginx directory index PAGASA publishes at pubfiles.pagasa.dost.gov.ph/tamss/weather// and returns each PDF's name, URL, last-modified time, and size. This tool returns file URLs only, never PDF bytes, so fetch a PDF yourself if you need its contents. Examples:

list_pagasa_advisory_files() latest weather advisories list_pagasa_advisory_files(kind="bulletin", limit=5) 5 newest cyclone bulletins list_pagasa_advisory_files(kind="stormsurge") storm surge folder, flagged stale

On failure: an unknown kind, or a limit outside 1 to 100, gives validation_error true and data_status "invalid_request". A 404, a body with no directory listing, zero parsed files, or a parser error on a 200 body gives data_status "indeterminate". A transport failure or a non-2xx status gives data_status "unavailable". All three carry files: [] and the real error in caveats.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`kind`	No	One of "weather_advisory", "bulletin", "stormsurge".	weather_advisory
`limit`	No	Max files to return, newest first (1 to 100, default 20).

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.8.0Sep 7, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description goes well beyond the readOnly/idempotent annotations by detailing the exact source (nginx directory index), the returned fields (name, URL, last-modified time, size), the fact that no PDF bytes are returned, and the full failure-mode taxonomy with data_status values. It also flags the storm surge folder as stale, adding meaningful behavioral context.

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?

The description is detailed but well structured: purpose is front-loaded, followed by mechanism, examples, and failure behavior. Every sentence adds useful information, and the examples with comments make the intended usage immediately understandable.

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?

Given the output schema exists, the description covers everything an agent needs: data source, return fields, the important caveat that only URLs are returned, and exhaustive failure-status behavior. Nothing needed for correct invocation is missing.

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?

The input schema already covers both parameters with defaults, ranges, and allowed values, so the baseline is 3. The description adds value by showing example calls, clarifying the meaning of kind as a folder selector, and confirming validation behavior for out-of-range limits and unknown kinds.

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 states a specific verb and resource: it lists PAGASA public PDF files from the pubfiles directory index, newest first. It clearly differentiates this from weather-content tools by stating it returns file URLs only, never PDF bytes, which distinguishes it from siblings like get_weather_alerts or get_weather_forecast.

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?

The description gives concrete usage examples and an explicit when-not-to-use condition: if you need PDF contents, fetch the PDF yourself. It does not name sibling alternatives or conditions for choosing them, but it clearly communicates the intended use case for this tool.

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

Deploy Server