PIA MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAX_RESULTS | No | Maximum results per query | 50 |
| PIA_API_KEY | Yes | Your PIA API key. Required for full functionality. | |
| PIA_API_URL | No | PIA API endpoint | https://mcp.programintegrity.org/ |
| REQUEST_TIMEOUT | No | API request timeout in seconds | 60 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pia_searchA | Search the Program Integrity Alliance (PIA) database of government oversight reports, recommendations, executive orders, legislation, and integrity data (GAO, OIG/Oversight.gov, CRS, DOJ, Congress.gov, Federal Register). One tool for all document search: scope by source/dataset/agency/date via filter, choose content vs titles via search_mode, sweep every source with wide, or discover filter values with facets_only. WHAT THE COUNTS MEAN: in 'content' mode (default) total_count and facet counts are TEXT CHUNKS / EXCERPTS — a single document is split into many chunks, so these counts are much larger than the number of documents and must NOT be reported as a document/report/article count. In 'titles' mode the counts are whole DOCUMENTS / ARTICLES. Use search_mode='titles' whenever the user asks how many documents, reports, or articles there are. Citations are very important to PIA users, so it is strongly expected that your answer: (1) gives every factual claim at least one clickable inline citation in the form [1], numbered sequentially from 1; (2) ends with a References section listing every source you cited, each reference on its own line (never multiple references on one line) — omit this section only for a pure count or summary with nothing specific to cite; and (3) includes a Find Out More section with the |
| pia_oversight_recommendationsA | Search oversight recommendations (Open Recommendations dataset) with facets enabled by default. Today's date is 2026-06-25. This dataset contains recommendations from GAO and Oversight.gov only — SourceDocumentDataSource filters for any other source will be ignored. Do NOT filter by SourceDocumentDataSet — this tool already targets the 'Open Recommendations' dataset automatically. IMPORTANT: When a text query is provided, do NOT add a referenced_agencies filter — the query handles relevance matching. Only use referenced_agencies when the query is empty (pure filter/facet lookups). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| pia_assistant_guidance | Comprehensive guidance for an LLM using PIA (GovQuery) tools: search strategy, citation format, and output structure |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have distinct focal areas: pia_search provides a general search across all PIA data sources, while pia_oversight_recommendations targets the Open Recommendations dataset specifically. However, since pia_search also includes recommendations, an agent could be uncertain which to use for a recommendation-focused query, though the detailed descriptions mitigate this.
Both tools share the 'pia_' prefix, which provides a consistent namespace, but one uses a verb ('search') and the other a noun phrase ('oversight_recommendations'), creating a slight structural inconsistency. With only two tools, the pattern is not fully established, but the names are descriptive and readable.
Two tools is on the thin side for a server covering multiple government data sources and document types, but both tools are highly parameterized and comprehensive in scope, so it is borderline rather than severely under-provisioned. The count feels reasonable if the server's purpose is narrowly focused on searching.
The server covers the search domain well, with one tool for broad document search and one for the specialized Open Recommendations dataset, including facets and filter discovery. Gaps include lack of a dedicated tool for retrieving individual documents or covering datasets other than recommendations, but these are workable via pia_search.