Openstates

Get Legislator

get_legislator

Read-onlyIdempotent

Fetch a single legislator by OpenStates person ID. Returns biographical info, current roles, prior offices, contact methods, sources.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`person_id`	Yes	OpenStates person ID (e.g., "ocd-person/...")

Output Schema

TableJSON Schema

Name	Required	Description
`name`	No	Full name
`email`	No	Email address
`image`	No	Image URL
`links`	No
`party`	No	Political party
`title`	No	Current title/role
`gender`	No	Gender
`chamber`	No	Chamber (upper/lower)
`offices`	No
`sources`	No	Source URLs
`district`	No	District identifier
`person_id`	No	OpenStates person ID
`birth_date`	No	Birth date
`death_date`	No	Death date
`given_name`	No	Given name
`family_name`	No	Family name
`other_names`	No	Alternative names
`jurisdiction`	No	State or jurisdiction
`openstates_url`	No	Link to OpenStates profile

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "person_id": "ocd-person/ca-john-doe"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "birth_date": {
+      "description": "Birth date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "chamber": {
+      "description": "Chamber (upper/lower)",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "death_date": {
+      "description": "Death date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "district": {
+      "description": "District identifier",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "email": {
+      "description": "Email address",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "family_name": {
+      "description": "Family name",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "gender": {
+      "description": "Gender",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "given_name": {
+      "description": "Given name",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "image": {
+      "description": "Image URL",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "jurisdiction": {
+      "description": "State or jurisdiction",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "links": {
+      "items": {
+        "properties": {
+          "note": {
+            "description": "Link note/description",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "url": {
+            "description": "Link URL",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "name": {
+      "description": "Full name",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "offices": {
+      "items": {
+        "properties": {
+          "address": {
+            "description": "Office address",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "classification": {
+            "description": "Office classification",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "email": {
+            "description": "Office email",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "description": "Office name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "voice": {
+            "description": "Phone number",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "openstates_url": {
+      "description": "Link to OpenStates profile",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "other_names": {
+      "description": "Alternative names",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "party": {
+      "description": "Political party",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "person_id": {
+      "description": "OpenStates person ID",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "sources": {
+      "description": "Source URLs",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "title": {
+      "description": "Current title/role",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "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 declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, covering the safety profile. The description adds valuable context about the return payload (biographical info, current roles, prior offices, contact methods, sources) without repeating annotation data.

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 a single, front-loaded sentence that states the action and the return contents. Every word earns its place, with zero fluff or repetition.

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?

This is a simple one-parameter tool with an output schema present. The description covers the purpose, input type, and return contents. Given the simplicity and annotations, there are no significant missing details.

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 schema description covers 100% of the parameter with format guidance (e.g., 'ocd-person/...'). The description merely reiterates 'OpenStates person ID' without adding new semantic detail, so it stays at the baseline for high schema coverage.

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 'Fetch a single legislator by OpenStates person ID' with a specific verb, singular resource, and input type. This distinguishes it from sibling tools like search_legislators, which imply broader search behavior.

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 implies usage when you have a person_id and need a single legislator's details. It does not explicitly name alternatives or exclusions, but the phrase 'a single legislator' provides clear context for when to use this tool versus searching.

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.