OpenPublica

Find governments by ZIP code

find_governments_by_zip

Read-only

Resolve a ZIP code to nearby tracked governments.

Convenience wrapper: geocodes the ZIP, then finds the governments OpenPublica
tracks nearest that point. Returns their `account_id`s plus the resolved
location. An empty `governments` list means none are tracked near that ZIP yet.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Max governments to return (1-50).
`postal_code`	Yes	A US ZIP code, e.g. '95814'.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint. The description adds meaningful detail beyond those: it reveals the internal geocoding step, states that results include `account_id`s plus the resolved location, and explains that an empty `governments` list is a valid outcome when none are tracked nearby.

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 three short sentences with no filler, and the core action is front-loaded before the wrapper explanation and return-value semantics. Every sentence earns its place.

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?

An output schema exists, so return-value structure does not need to be repeated. For a simple two-parameter lookup, the description adds the geocoding behavior, empty-list interpretation, and nearby-scope context an agent needs to interpret results correctly.

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?

The input schema covers 100% of parameters and already describes postal_code as a US ZIP code and limit as a 1-50 count. The description does not elaborate on either parameter beyond the schema, so the baseline of 3 applies.

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?

The description opens with a concrete action: 'Resolve a ZIP code to nearby tracked governments', naming both the input (ZIP) and the resource (governments tracked by OpenPublica). It is clearly distinct from the sibling find_governments_by_name, though it does not explicitly name alternatives.

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?

'Convenience wrapper: geocodes the ZIP, then finds...' implies the intended trigger is having a ZIP code and wanting the nearest tracked governments. It gives no when-not or alternative-routing guidance, so it stops short of a 5.

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

All OpenPublica tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool targets a clear, distinct operation: government discovery, meeting search, transcript search, document listing, and document reading are all cleanly separated. The three find_governments tools overlap in purpose but are differentiated by input type (name, ZIP, coordinates), and the descriptions explicitly call out when to prefer one over another.

Naming Consistency5/5

Tool names follow a consistent and predictable verb_noun pattern: find_governments_by_*, get_*, list_*, search_*, read_*, and discover_*. The qualifiers are descriptive and parallel, making the intended action and resource obvious from the name alone.

Tool Count5/5

At 15 tools, the set is at the upper end of the ideal range but every tool earns its place by covering a distinct capability across two related domains: meetings and government documents. There is no filler or redundancy; the count feels well-scoped for the server's stated purpose.

Completeness5/5

For a read-only public-records service, the surface is remarkably complete: government resolution by name/ZIP/coordinates, coverage, stats, meeting discovery/search/retrieval, transcript-level search, and document listing/search/reading all have dedicated tools. There are no obvious dead ends—every search path leads to a retrieval tool that can produce citable quotes, pages, or full transcripts.

Resources

Need Help?