Skip to main content
Glama
xmpuspus

ph-civic-data-mcp

by xmpuspus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Search PhilGEPS procurement notices

search_procurement
Read-onlyIdempotent

Search Philippine government procurement notices using PhilGEPS data, filtering by keyword, agency, region, or date range. Handles data outages and invalid input with explicit error responses.

Instructions

Search PH government procurement from PhilGEPS open data.

Note: the PhilGEPS public portal does not expose server-side search for external clients, so this tool fetches the latest ~100 bid notices and filters them in-memory. Data is cached 6 hours. Keyword/agency/region filters are applied client-side (case-insensitive substring match). Examples:

search_procurement(keyword="flood") search_procurement(keyword="", agency="DPWH", limit=10)

On failure: returns {results: [], upstream_error: true, data_status: "unavailable", caveats: [...]} instead of a bare list, so an outage is never read as "no matching notices". A date_from or date_to that does not parse returns {results: [], validation_error: true, data_status: "invalid_request"} before any fetch, naming the bad value.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 20, max 100).
agencyNoPartial match on procuring entity name.
regionNoPH region filter (partial match).
date_toNo
keywordYesSearch term matched against title + agency + classification.
date_fromNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.5.0
    • addedOutput schema / properties / result / anyOf
      Added value: +[
+  {
+    "items": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "additionalProperties": true,
+    "type": "object"
+  }
+]
    • removedOutput schema / properties / result / items
      Removed value: -{
-  "additionalProperties": true,
-  "type": "object"
-}
    • removedOutput schema / properties / result / type
      Removed value: -"array"
  2. Addedv0.4.0
  3. Removedv1.0.4
  4. Addedv1.0.2

TDQS

A4.4/5.0
Behavior5/5

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

Describes failure behavior in detail: upstream outage returns a structured object with upstream_error and data_status 'unavailable', invalid dates return validation_error; also discloses caching and client-side filtering. This goes beyond the readOnly/idempotent annotations.

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?

Description is well-organized: one-sentence purpose, a note on implementation constraints, examples, and a failure-mode paragraph. No redundant content; all sentences carry useful operational information.

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?

Given the tool's moderate complexity, the description covers caching, filter behavior, examples, and error shapes. It does not explain date formats, but the core calling contract is sufficiently specified and the output schema/annotations fill remaining context.

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 covers limit, agency, region, and keyword decently. Description adds that filters are case-insensitive substring matches and that date_from/date_to are validated. However, date_from/date_to lack format and semantic meaning (e.g., publication date) in both schema and description.

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?

Clearly names the resource (PH government procurement from PhilGEPS open data) and the action (search). The tool name and title reinforce the scope, and it is distinct from nearby search tools for infrastructure or datasets.

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?

Provides concrete usage notes: the portal lacks server-side search, so it fetches ~100 notices and filters in-memory; filters are case-insensitive substring matches; data is cached 6 hours. Examples illustrate valid calls including keyword-only and keyword+agency+limit. It does not explicitly contrast with sibling search tools, but the usage context is 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