Skip to main content
Glama
julianken

civic-awareness-mcp

by julianken

recent_bills

Retrieve recently updated U.S. state legislative bills by jurisdiction. Filter by chamber, session, sponsor, classification, subject, or date range to find specific bills or track legislative activity.

Instructions

List U.S. state legislative bills from OpenStates. Defaults to the last days (default 7) of recently-updated bills. Optional filters: chamber, session, sponsor_entity_id (civic entity UUID, resolved to OpenStates OCD id), classification, subject, introduced_since/until, updated_since/until, sort. Any explicit date range overrides days. Pass a jurisdiction like 'us-tx' or 'us-ca'; '*' queries all cached jurisdictions locally. Useful for 'what did this legislator introduce' and 'recent bills on ' queries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoLook-back window in days. Ignored when any explicit introduced_since/until or updated_since/until is set.
sortNoupdated_desc
limitNoOptional row cap. Without explicit date filters, caps recency-sorted rows from a 365-day lookback.
chamberNo
sessionNo
subjectNo
jurisdictionYesJurisdiction like 'us-tx' or 'us-ca'. '*' queries all cached jurisdictions locally (no upstream fetch).
updated_sinceNo
updated_untilNo
classificationNo
introduced_sinceNo
introduced_untilNo
sponsor_entity_idNoCivic entity UUID; resolved to OpenStates OCD person id before upstream fetch.
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses defaults, override behavior, and the wildcard jurisdiction for local caching. However, it does not state that the operation is read-only, mention rate limits or authentication needs, or describe any side effects. This is adequate but leaves gaps.

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 efficient and front-loaded, starting with the core purpose. It packs multiple pieces of information into a single paragraph without fluff. Could be slightly more structured (e.g., use bullet points for filters), but it is concise and readable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and 13 parameters (31% coverage), the description provides good context for core functionality and use cases. However, it omits details about return format, pagination, error cases, and does not fully compensate for the low parameter coverage. It is functional but not fully complete for complex queries.

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 31%, so the description must compensate. It lists many optional filters (chamber, session, subject, etc.) and explains `sponsor_entity_id` resolution and jurisdiction wildcard. However, it does not add detailed semantics for all 13 parameters (e.g., classification, `limit` behavior could be clearer). The description adds some value beyond the schema but is not comprehensive.

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 clearly states the verb 'List' and the resource 'U.S. state legislative bills from OpenStates', with details on defaults and optional filters. It distinguishes from siblings like get_bill (single bill) and recent_votes (votes) by focusing on recent bills, but does not explicitly contrast with all siblings.

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 explains the default `days` parameter, how explicit date ranges override it, and mentions specific use cases like 'what did this legislator introduce'. It lacks explicit guidance on when not to use this tool versus alternatives, but the context is sufficient for an agent to infer appropriate usage.

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/julianken/civic-awareness-mcp'

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