Skip to main content
Glama

Search Events

openstates_search_events
Read-onlyIdempotent

Search hearings, floor sessions, and committee meetings. jurisdiction is required — the Open States events endpoint has no all-states search, so scope every call to a single state; use openstates_list_jurisdictions to pick one. Experimental — most states do not publish event data to Open States. Use after and before to scope to a date range. Set require_bills=true to filter to events with bills on the agenda, which is the most useful filter for tracking legislation through committee. Use include=agenda,participants for full meeting context. Empty results often indicate the state lacks event data rather than no events occurring.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (1-indexed).
afterNoISO 8601 datetime — events starting after this time. Use to find upcoming hearings.
beforeNoISO 8601 datetime — events starting before this time.
includeNoRelated data to inline. "agenda" includes the meeting agenda with bill references. "participants" includes the committee or chamber hosting the event. "links" and "media" add related URLs and recordings, "documents" the attached files, and "sources" the provenance URLs behind the record.
per_pageNoResults per page. Maximum 20.
jurisdictionYesState name, abbreviation, or OCD-ID. Required — the Open States events endpoint has no all-states search, so every call must be scoped to a single jurisdiction.
require_billsNoWhen true, only return events with at least one bill on the agenda. Most useful for tracking legislation through committee.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoCurrent page returned.
errorNoPresent when the call failed. Absent on success.
noticeNoRecovery hint when results are empty. Absent when results are returned.
maxPageNoTotal pages available.
resultsNoEvents matching the search criteria.
paginationNoPagination metadata.
totalCountNoTotal events matching the query across all pages.
coverageNoteNoEvent data is experimental — most states do not publish event data to Open States. Empty results may indicate the state lacks data, not that no events occurred.
appliedFiltersNoFilters applied to this query as the server received them, for agent self-verification of zero or unexpected results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedOutput schema / anyOf
      Added value: +[
      +  {
      +    "not": {
      +      "required": [
      +        "error"
      +      ]
      +    },
      +    "required": [
      +      "results",
      +      "pagination",
      +      "totalCount",
      +      "page",
      +      "maxPage",
      +      "coverageNote",
      +      "appliedFilters"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "error"
      +    ]
      +  }
      +]
    • addedOutput schema / properties / error
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "Present when the call failed. Absent on success.",
      +  "properties": {
      +    "code": {
      +      "description": "JSON-RPC error code for this failure.",
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    },
      +    "data": {
      +      "additionalProperties": {},
      +      "properties": {
      +        "reason": {
      +          "description": "Machine-readable failure mode. Declared by this tool: `upstream_timeout`: Open States did not answer within the per-request timeout — the query is too broad. `invalid_page`: Open States rejected the request as not found — page is past the last page for this query. Other values are possible when a failure originates below the handler.",
      +          "examples": [
      +            "upstream_timeout",
      +            "invalid_page"
      +          ],
      +          "type": "string"
      +        },
      +        "recovery": {
      +          "additionalProperties": {},
      +          "description": "Actionable next step for the caller.",
      +          "properties": {
      +            "hint": {
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "hint"
      +          ],
      +          "type": "object"
      +        },
      +        "retryable": {
      +          "description": "Whether retrying may succeed.",
      +          "type": "boolean"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "message": {
      +      "description": "Human-readable description of what went wrong.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "code",
      +    "message"
      +  ],
      +  "type": "object"
      +}
    • removedOutput schema / required
      Removed value: -[
      -  "results",
      -  "pagination",
      -  "totalCount",
      -  "page",
      -  "maxPage",
      -  "coverageNote",
      -  "appliedFilters"
      -]
  2. Changed4 schema fields changed
    • changedOutput schema / properties / results / items / properties / documents / items / properties / note / description
      Previous value: -"Document description."New value: +"Document description. Empty string when Open States recorded no description."
    • changedOutput schema / properties / results / items / properties / links / items / properties / note / description
      Previous value: -"Link description."New value: +"Link description. Empty string when Open States recorded no description."
    • changedOutput schema / properties / results / items / properties / media / items / properties / note / description
      Previous value: -"Media description."New value: +"Media description. Empty string when Open States recorded no description."
    • changedOutput schema / properties / results / items / properties / sources / items / properties / note / description
      Previous value: -"Source note."New value: +"Source note. Empty string when Open States recorded no note."
  3. Changed3 schema fields changed
    • changedInput schema / properties / jurisdiction / description
      Previous value: -"State name, abbreviation, or OCD-ID. Required — the Open States events endpoint has no all-states search and rejects requests that omit it."New value: +"State name, abbreviation, or OCD-ID. Required — the Open States events endpoint has no all-states search, so every call must be scoped to a single jurisdiction."
    • addedInput schema / properties / jurisdiction / minLength
      Added value: +1
    • addedInput schema / required
      Added value: +[
      +  "jurisdiction"
      +]
  4. Changed7 schema fields changed
    • changedInput schema / properties / include / description
      Previous value: -"Related data to inline. \"agenda\" includes the meeting agenda with bill references. \"participants\" includes the committee or chamber hosting the event."New value: +"Related data to inline. \"agenda\" includes the meeting agenda with bill references. \"participants\" includes the committee or chamber hosting the event. \"links\" and \"media\" add related URLs and recordings, \"documents\" the attached files, and \"sources\" the provenance URLs behind the record."
    • addedOutput schema / properties / results / items / properties / documents
      Added value: +{
      +  "description": "Document links when include=documents is requested.",
      +  "items": {
      +    "additionalProperties": false,
      +    "description": "Document link record.",
      +    "properties": {
      +      "note": {
      +        "description": "Document description.",
      +        "type": "string"
      +      },
      +      "url": {
      +        "description": "Document URL.",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "url",
      +      "note"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / results / items / properties / links
      Added value: +{
      +  "description": "Event links when include=links is requested.",
      +  "items": {
      +    "additionalProperties": false,
      +    "description": "External link record.",
      +    "properties": {
      +      "note": {
      +        "description": "Link description.",
      +        "type": "string"
      +      },
      +      "url": {
      +        "description": "Link URL.",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "url",
      +      "note"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / results / items / properties / media
      Added value: +{
      +  "description": "Media links when include=media is requested.",
      +  "items": {
      +    "additionalProperties": false,
      +    "description": "Media link record.",
      +    "properties": {
      +      "note": {
      +        "description": "Media description.",
      +        "type": "string"
      +      },
      +      "url": {
      +        "description": "Media URL.",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "url",
      +      "note"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / properties / results / items / properties / participants / items / properties / role / description
      Previous value: -"Participant role."New value: +"Participant role. Absent when upstream omits it."
    • changedOutput schema / properties / results / items / properties / participants / items / required
      Previous value: -[
      -  "name",
      -  "entity_type",
      -  "role"
      -]New value: +[
      +  "name",
      +  "entity_type"
      +]
    • addedOutput schema / properties / results / items / properties / sources
      Added value: +{
      +  "description": "Provenance sources when include=sources is requested.",
      +  "items": {
      +    "additionalProperties": false,
      +    "description": "Source record.",
      +    "properties": {
      +      "note": {
      +        "description": "Source note.",
      +        "type": "string"
      +      },
      +      "url": {
      +        "description": "Source URL.",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "url",
      +      "note"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  5. Changed1 schema field changed
    • changedInput schema / properties / jurisdiction / description
      Previous value: -"State name, abbreviation, or OCD-ID. Omitting searches across all states."New value: +"State name, abbreviation, or OCD-ID. Required — the Open States events endpoint has no all-states search and rejects requests that omit it."
  6. Changed4 schema fields changed
    • addedInput schema / properties / after / pattern
      Added value: +"^\\d{4}-\\d{2}-\\d{2}(T[\\d:.Z+-]+)?$"
    • addedInput schema / properties / before / pattern
      Added value: +"^\\d{4}-\\d{2}-\\d{2}(T[\\d:.Z+-]+)?$"
    • addedOutput schema / properties / appliedFilters
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Filters applied to this query as the server received them, for agent self-verification of zero or unexpected results.",
      +  "properties": {
      +    "after": {
      +      "description": "after datetime filter as received.",
      +      "type": "string"
      +    },
      +    "before": {
      +      "description": "before datetime filter as received.",
      +      "type": "string"
      +    },
      +    "jurisdiction": {
      +      "description": "Jurisdiction filter as received.",
      +      "type": "string"
      +    },
      +    "page": {
      +      "description": "Page number requested.",
      +      "type": "number"
      +    },
      +    "per_page": {
      +      "description": "Results per page requested.",
      +      "type": "number"
      +    },
      +    "require_bills": {
      +      "description": "require_bills flag as received.",
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "require_bills",
      +    "page",
      +    "per_page"
      +  ],
      +  "type": "object"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "results",
      -  "pagination",
      -  "totalCount",
      -  "page",
      -  "maxPage",
      -  "coverageNote"
      -]New value: +[
      +  "results",
      +  "pagination",
      +  "totalCount",
      +  "page",
      +  "maxPage",
      +  "coverageNote",
      +  "appliedFilters"
      +]
  7. Changed3 schema fields changed
    • addedOutput schema / properties / totalCount
      Added value: +{
      +  "description": "Total events matching the query across all pages.",
      +  "type": "number"
      +}
    • removedOutput schema / properties / totalItems
      Removed value: -{
      -  "description": "Total events matching the query across all pages.",
      -  "type": "number"
      -}
    • changedOutput schema / required
      Previous value: -[
      -  "results",
      -  "pagination",
      -  "totalItems",
      -  "page",
      -  "maxPage",
      -  "coverageNote"
      -]New value: +[
      +  "results",
      +  "pagination",
      +  "totalCount",
      +  "page",
      +  "maxPage",
      +  "coverageNote"
      +]
  8. Changed8 schema fields changed
    • addedOutput schema / properties / coverageNote
      Added value: +{
      +  "description": "Event data is experimental — most states do not publish event data to Open States. Empty results may indicate the state lacks data, not that no events occurred.",
      +  "type": "string"
      +}
    • removedOutput schema / properties / coverage_note
      Removed value: -{
      -  "description": "Event data is experimental — most states do not publish event data to Open States. Empty results may indicate the state lacks data, not that no events occurred.",
      -  "type": "string"
      -}
    • addedOutput schema / properties / maxPage
      Added value: +{
      +  "description": "Total pages available.",
      +  "type": "number"
      +}
    • removedOutput schema / properties / message
      Removed value: -{
      -  "description": "Recovery hint when results are empty. Absent when results are returned.",
      -  "type": "string"
      -}
    • addedOutput schema / properties / notice
      Added value: +{
      +  "description": "Recovery hint when results are empty. Absent when results are returned.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / page
      Added value: +{
      +  "description": "Current page returned.",
      +  "type": "number"
      +}
    • addedOutput schema / properties / totalItems
      Added value: +{
      +  "description": "Total events matching the query across all pages.",
      +  "type": "number"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "results",
      -  "pagination",
      -  "coverage_note"
      -]New value: +[
      +  "results",
      +  "pagination",
      +  "totalItems",
      +  "page",
      +  "maxPage",
      +  "coverageNote"
      +]
  9. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare readOnlyHint, openWorldHint, and idempotentHint, which cover safety and repeatability. The description adds meaningful behavioral context beyond that: the experimental nature, the fact that most states lack event data, and the interpretation of empty results. No contradictions with annotations.

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 about four sentences and front-loads the core purpose and the mandatory jurisdiction constraint. It is reasonably tight, though some advice (like require_bills and include) is also present in the schema and could be considered slightly redundant, keeping it from a 5.

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?

With an output schema present, the description need not explain return values. It covers the sole required parameter, the experimental caveat, common filters, and empty-result interpretation—everything an agent needs to correctly scope and call the tool. It is fully complete for the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so each parameter already has solid descriptions. The description adds extra value by explaining the rationale behind jurisdiction (no all-states search), suggesting after for upcoming hearings, and highlighting require_bills for tracking legislation. This goes just beyond the schema, warranting a 4.

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 hearings, floor sessions, and committee meetings, which is a specific verb and resource. It distinguishes from sibling get_event by focusing on search, and the opening sentence leaves no ambiguity about what the tool does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit, actionable guidance: jurisdiction is required and why, use openstates_list_jurisdictions to choose one, use after/before for date scoping, require_bills for filtering, and include for context. It also warns about experimental status and how to interpret empty results, which directly informs usage decisions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.