Skip to main content
Glama
xmpuspus

ph-civic-data-mcp

by xmpuspus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Philippine health indicators

get_health_indicators
Read-onlyIdempotent

Retrieve Philippine health indicators including maternal mortality ratio and total fertility rate. Optionally specify a free-text indicator to access matching health statistics.

Instructions

National health indicators from PSA OpenSTAT (subject 1D).

With no argument, returns the curated national headline set: maternal mortality ratio and total fertility rate. Pass a free-text indicator to fuzzy-match any table published under the Health subject. The available list is browse-discovered, never hardcoded. Examples:

get_health_indicators() maternal mortality ratio and fertility rate get_health_indicators(indicator="fertility") one matching table

On failure: a catalog browse failure sets data_status "unavailable" and upstream_error true, with an empty indicators list. A keyword that matches no table sets data_status "success" with an empty indicators list and a caveat, not an error flag. A partial fetch failure across matched tables sets data_status "indeterminate" and upstream_error true. validation_error stays false in every case.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indicatorNoOptional free-text indicator name, for example "maternal mortality", "fertility". None returns the default headline set.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.8.0
    • changedInput schema / properties / indicator / description
      Previous value: -"Optional free-text indicator name, e.g. \"maternal mortality\",\n       \"fertility\". None returns the default headline set."New value: +"Optional free-text indicator name, for example \"maternal\n       mortality\", \"fertility\". None returns the default headline set."
  2. Addedv0.4.0

TDQS

A4.8/5.0
Behavior5/5

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

The description is fully transparent about behavior, including failure modes with data_status updates, caveats, and upstream_error flags. It adds context beyond the annotations by detailing specific error scenarios, and does not contradict any annotation.

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 concise yet comprehensive, using structured sections for examples and failure modes. It front-loads the core purpose and avoids extraneous detail, making it easy to scan.

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 tool with an output schema, the description adequately covers return behavior (headline set, indicators array, data_status, caveats, error flags) without needing to restate the schema. It is complete for an agent to understand what to expect and how to handle edge cases.

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?

The schema already documents the optional indicator parameter with examples, and the description reinforces this by explaining the fuzzy-match behavior, the default null behavior, and that the list is browse-discovered rather than hardcoded. This goes well beyond the baseline coverage.

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 the tool's purpose: retrieving national health indicators from PSA OpenSTAT (subject 1D). It distinguishes itself from sibling tools by focusing specifically on health data, with explicit examples of default outputs and fuzzy matching behavior.

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 explains when to use the tool: with no argument for a default headline set, or with an indicator name for fuzzy matching. It does not explicitly contrast with alternative tools such as search_psa_catalog, but the specialization to health indicators makes the appropriate use case clear.

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

Deploy Server

Other Tools