Skip to main content
Glama
Program-Integrity-Alliance

PIA MCP Server

Official

pia_search

Search government oversight reports, recommendations, and legislation from GAO, OIG, CRS, DOJ, Congress.gov, and Federal Register with filters for source, agency, and date, plus facet discovery.

Instructions

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 govquery_url so the user can open the full result set. Please do not present findings from these results without their inline citations and References section. Counts from free-text queries are approximate, because semantic search matches variations of the search terms.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (1-based). Ignored when wide=true.
wideNoWhen true, sweep ALL sources/datasets in parallel and merge into one de-duplicated, score-ranked list. Use for the most comprehensive cross-source view.
limitNoOptional hard cap on results (alias for page_size).
queryYesSearch query — natural language or keywords. Use "" or "*" to match all documents (for pure filter/facet lookups).
filterNoOData filter to scope results (boolean logic + grouping). Source: SourceDocumentDataSource eq 'GAO' (valid: GAO, Oversight.gov, CRS, Department of Justice, Congress.gov, Federal Register). Agency: referenced_agencies/any(a: a eq 'Department of Defense (DOD)'). Dataset: SourceDocumentDataSet eq 'executive orders'. To restrict to one source, pass its SourceDocumentDataSource filter.
page_sizeNoResults per page (max 50). Per-source before merge when wide=true.
facets_onlyNoReturn ONLY facet counts (available filter values), no document results — to discover filters before drilling in. Implies include_facets.
search_modeNo'content' searches the full-text (chunked) index — total_count and facet counts are TEXT CHUNKS / EXCERPTS, NOT documents: one document is split into many chunks, so the counts EXCEED the number of documents. 'titles' searches the document-level index — total_count and facet counts are whole DOCUMENTS / ARTICLES, and it's faster for locating a specific document. Use 'titles' whenever the user asks how many documents / reports / articles there are.content
include_facetsNoInclude per-dimension facet counts (source, status, priority, agency, theme, …) alongside results.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
outputYes
Behavior5/5

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

With no annotations, the description carries full behavioral disclosure. It explicitly explains that counts in content mode are text chunks, not documents, that counts are approximate for free-text queries, and it mandates citation and References formatting plus a Find Out More section. This is rich, actionable transparency beyond the schema.

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?

The description is longer than average but well-structured with labeled sections (WHAT THE COUNTS MEAN) and front-loaded purpose. Each sentence adds significant guidance for a complex tool, though some redundancy with schema descriptions could be trimmed.

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 tool's complexity (9 parameters, output schema present), the description adds essential context: count semantics, citation requirements, wide-mode behavior, and facet discovery. It is complete enough for an agent to invoke the tool correctly and interpret results accurately.

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 description coverage is 100%, so parameters are already well documented. The description adds clarifying context around count interpretation and the difference between content vs titles modes, but much of this is also present in the schema's parameter descriptions. It adds marginal value without fully compensating for any gaps.

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 searches the PIA database of government oversight reports and related documents, with a specific verb ('Search') and resource ('PIA database'). It distinguishes itself as 'One tool for all document search' and covers scoping modes, which separates it from the sibling tool pia_oversight_recommendations.

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 clear guidance on when to use specific modes, such as using search_mode='titles' when users ask for document counts, and identifies wide/facets_only as specialized uses. It does not explicitly mention when to avoid this tool or name the sibling as an alternative, so it stops shy of full when/when-not guidance.

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/Program-Integrity-Alliance/pia-mcp-local'

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