Openstates

Get Bill

get_bill

Read-onlyIdempotent

Fetch a single bill with full detail: versions, sponsorships, related/companion bills, actions, and votes. Pass the OpenStates ID (e.g., "ocd-bill/abc...") or a state/session/identifier triple.

Input Schema

Name	Required	Description
`session`	No	Session ID, per state (Ohio "136", California "20252026"); a year or year range is resolved to the state's session. Use with jurisdiction + identifier.
`identifier`	No	Bill identifier within the session (e.g., "AB-123")
`jurisdiction`	No	State code (use with session + identifier)
`openstates_id`	No	OpenStates bill ID (preferred, e.g., "ocd-bill/...")

Output Schema

Name	Required	Description
`title`	No	Bill title
`votes`	No
`actions`	No
`chamber`	No	Chamber (upper/lower) or organization
`session`	No	Legislative session
`sources`	No	Source URLs
`subject`	No	Subject tags
`sponsors`	No
`versions`	No
`identifier`	No	Bill identifier
`jurisdiction`	No	State or jurisdiction name
`latest_action`	No	Description of latest action
`openstates_id`	No	OpenStates bill ID
`classification`	No	Bill type classifications
`openstates_url`	No	Link to OpenStates page
`latest_action_date`	No	Date of latest action

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 27, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "openstates_id": "ocd-bill/ca20232024-ab-123"
-  },
-  {
-    "identifier": "HB-456",
-    "jurisdiction": "TX",
-    "session": "20232024"
-  }
-]New value: +[
+  {
+    "openstates_id": "ocd-bill/ca20232024-ab-123"
+  },
+  {
+    "identifier": "SB 2",
+    "jurisdiction": "TX",
+    "session": "89R"
+  }
+]

changedInput schema / properties / session / description

Previous value: -"Session ID (use with jurisdiction + identifier)"New value: +"Session ID, per state (Ohio \"136\", California \"20252026\"); a year or year range is resolved to the state's session. Use with jurisdiction + identifier."

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "openstates_id": "ocd-bill/ca20232024-ab-123"
+  },
+  {
+    "identifier": "HB-456",
+    "jurisdiction": "TX",
+    "session": "20232024"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "actions": {
+      "items": {
+        "properties": {
+          "classification": {
+            "description": "Action classifications",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "date": {
+            "description": "Action date",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "description": {
+            "description": "Action description",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "chamber": {
+      "description": "Chamber (upper/lower) or organization",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "classification": {
+      "description": "Bill type classifications",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "identifier": {
+      "description": "Bill identifier",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "jurisdiction": {
+      "description": "State or jurisdiction name",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "latest_action": {
+      "description": "Description of latest action",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "latest_action_date": {
+      "description": "Date of latest action",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "openstates_id": {
+      "description": "OpenStates bill ID",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "openstates_url": {
+      "description": "Link to OpenStates page",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "session": {
+      "description": "Legislative session",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "sources": {
+      "description": "Source URLs",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "sponsors": {
+      "items": {
+        "properties": {
+          "classification": {
+            "description": "Sponsor classification",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "description": "Sponsor name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "person_id": {
+            "description": "OpenStates person ID",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "primary": {
+            "description": "Is primary sponsor",
+            "type": [
+              "boolean",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "subject": {
+      "description": "Subject tags",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "title": {
+      "description": "Bill title",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "versions": {
+      "items": {
+        "properties": {
+          "date": {
+            "description": "Version date",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "links": {
+            "items": {
+              "properties": {
+                "media_type": {
+                  "description": "MIME type",
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                },
+                "url": {
+                  "description": "Link URL",
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "note": {
+            "description": "Version note",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "votes": {
+      "items": {
+        "properties": {
+          "counts": {
+            "description": "Vote counts by option",
+            "type": "array"
+          },
+          "id": {
+            "description": "Vote ID",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "motion": {
+            "description": "Motion text",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "result": {
+            "description": "Vote result",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "start_date": {
+            "description": "Vote date",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedMay 13, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already establish that this is read-only, idempotent, and non-destructive, so the description does not need to restate that. It adds useful behavioral context by specifying the exact composition of the returned bill (versions, sponsorships, related/companion bills, actions, and votes) and by explaining the two accepted identifier modes. This goes beyond the structured fields without contradicting them.

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?

Two sentences, no filler. The primary action and return content are front-loaded, and the invocation guidance is presented as a compact either/or. 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?

The description is complete for an agent deciding whether and how to call this tool: it names the resource, states what is returned, and gives both valid identification forms. The output schema and annotations already cover return shape and safety, so nothing essential is missing.

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 description coverage is 100%, so the baseline is 3, but the description adds meaningful grouping: it states that the state/session/identifier parameters form a triple and that openstates_id is an alternative, not a co-requisite. This clarifies the otherwise-missable either/or relationship among four individually optional parameters.

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 ('Fetch') and a clear resource ('a single bill'), then enumerates the returned detail: versions, sponsorships, related/companion bills, actions, and votes. The word 'single' differentiates it from sibling search_bills, and the alternative identifier forms make the tool's scope immediately obvious.

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

Usage Guidelines3/5

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

The description implies when to use this tool—when you need one specific bill with full detail—and explains how to identify that bill. However, it never explicitly contrasts it with sibling tools such as search_bills or get_legislator, and it gives no 'when not to use' guidance. The usage context is clear but must be inferred.

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

All Openstates tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.