Skip to main content
Glama
xmpuspus

ph-civic-data-mcp

search_infra_projects

Search Philippine government infrastructure projects by keyword, region, province, year, cost, or status. Data sourced from PhilGEPS open notice listing.

Instructions

Search Philippine government infrastructure projects.

Backed by PhilGEPS open notice listing filtered for infra-related work (construction / road / bridge / flood control / drainage / school building / civil works). Source: https://www.philgeps.gov.ph/. Approved budget amounts are not published in the open notice listing, so cost_php is null in most records. The DPWH transparency portal API is currently blocked by Cloudflare and not used.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordNoTitle/agency substring (e.g. 'flood control', 'bridge').
regionNoPH region filter (partial match against agency text).
provinceNoProvince name filter (partial match).
yearNoFilter publish date to this calendar year.
min_cost_phpNoMinimum approved cost in PHP (filters out null-cost records when set).
statusNoStatus filter (partial match, e.g. 'open', 'awarded').
limitNoMax results (default 25, capped at 100).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided, so description carries full burden. Discloses key behavioral aspects: data source (PhilGEPS), common null cost values, and the inability to use DPWH API. Lacks details on read-only nature, rate limits, pagination, or result ordering.

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?

Description is concise with 4 sentences, front-loading the purpose. Could be slightly more structured, but every sentence adds value. No fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, source, and a key limitation. Does not explain output format or pagination, but output schema exists. Lacks notes on status values or ordering. Adequate for a search tool with good schema.

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

Parameters3/5

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

Schema coverage is 100% with detailed parameter descriptions. The description adds marginal value by explaining why 'min_cost_php' often yields null results and provides example keyword values. Baseline is 3 due to high schema coverage.

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?

Description clearly states the tool searches Philippine government infrastructure projects, with specific examples of included work types. Differentiates from sibling tools implicitly by focusing solely on infrastructure, but does not explicitly contrast with 'search_procurement' or other related tools.

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?

Provides context about data source and limitations (cost_php null, DPWH API blocked), which helps decide when to use. However, no explicit when-not or alternative recommendations relative to sibling tools like 'search_procurement' or 'get_infra_project'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/xmpuspus/ph-civic-data-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server