OpenPublica

Get government meeting stats

get_government_stats

Read-only

Get meeting-activity stats for a government over a recent window.

Returns total meeting count, a per-day activity map, and a breakdown of meeting categories — useful for "how active has X been lately?" questions.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`days`	No	Look-back window in days (1-365).
`government_id`	Yes	account_id of the government, or 'all' for corpus-wide stats.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4.3/5.0

Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral context by specifying that the tool produces aggregate counts, a per-day map, and category breakdowns rather than raw records, and frames it as activity analysis over a window.

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 compact and front-loaded: it states the purpose first, then lists the return contents and a usage cue. Every sentence earns its place without redundant phrasing or boilerplate.

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 output schema exists, the input schema fully documents both parameters, and the description conveys the tool's scope and result shape, nothing essential is missing for an agent to select and invoke this tool 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?

Schema description coverage is 100%, and both parameters already have meaningful descriptions including the 'all' special value for government_id and the 1-365 range for days. The description does not add parameter-level detail, but it does not need to because the schema carries that burden.

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 uses a specific verb and resource: "Get meeting-activity stats for a government over a recent window", then enumerates exactly what is returned. This clearly distinguishes it from siblings like get_government_info, list_recent_meetings, and search_meetings_semantic.

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 provides clear context by saying it is useful for questions like "how active has X been lately?". It does not explicitly name alternatives or state when not to use the tool, but the intent and appropriate scenario are evident from the description and the sibling tool names.

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?