Skip to main content
Glama

congressgov-mcp-server

Congress.gov Roll Votes

congressgov_roll_votes
Read-onlyIdempotent

Retrieve U.S. congressional roll call votes and individual member voting positions for either chamber. Set 'chamber' to 'house' (default, from the Congress.gov API) or 'senate' (from the Senate's official LIS feed). Use 'list' to find votes by congress and session (newest first by default), 'get' for vote details (question, result, tallies, party breakdown, associated bill/nomination/amendment), or 'members' for how each member voted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoResults per page (1-250).
orderNoSort order for 'list'. 'recent' (default) returns newest first; 'oldest' returns ascending. House sorts by vote update date (with 'recent', offset=0 always returns the strictly newest page); Senate sorts by roll call number. Ignored by 'get' and 'members'.recent
offsetNoPagination offset.
chamberNoChamber whose votes to query. 'house' (default) draws from the Congress.gov API; 'senate' draws from the Senate's official LIS roll-call feed. Roll call numbers reset each session and are specific to one chamber.house
sessionYesSession number (1 or 2). Odd years are session 1, even years session 2.
congressYesCongress number.
operationYesWhich data to retrieve.
voteNumberNoRoll call vote number. Required for 'get' and 'members'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoResult rows. Per-tool item shape is rendered in the markdown body.
voteNoDynamic upstream JSON record.
errorNoPresent when the call failed. Absent on success.
noticeNoGuidance when results are empty, a page is past the end, or a caveat applies.
paginationNoPagination metadata: total count and next offset.
totalCountNoTotal results across all pages.
effectiveQueryNoThe browse scope and applied filters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `not_found`: A requested bill, member, committee, report, vote, or nomination does not exist in Congress.gov. `rate_limited`: The Congress.gov API rate limit (5,000 requests/hour per key) was exceeded. `invalid_request`: Congress.gov rejected the request as malformed — a bad date range or an identifier with an unexpected shape. `upstream_error`: Congress.gov returned an unexpected error (5xx or another non-2xx status). Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `not_found`: A requested bill, member, committee, report, vote, or nomination does not exist in Congress.gov. `rate_limited`: A process-local attempt budget or the shared upstream credential/IP quota was reached; upstream hourly limits vary and DEMO_KEY also has a daily quota. `invalid_request`: Congress.gov rejected the request as malformed — a bad date range or an identifier with an unexpected shape. `upstream_error`: Congress.gov returned an unexpected error (5xx or another non-2xx status). `upstream_timeout`: The Congress.gov request deadline expired or the upstream returned an HTTP timeout response. `incompatible_identity`: A list operation carries an entity identifier that only a detail operation uses. Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / error / properties / data / properties / reason / examples
      Previous value: -[
      -  "not_found",
      -  "rate_limited",
      -  "invalid_request",
      -  "upstream_error"
      -]New value: +[
      +  "not_found",
      +  "rate_limited",
      +  "invalid_request",
      +  "upstream_error",
      +  "upstream_timeout",
      +  "incompatible_identity"
      +]
  2. Changed1 schema field changed
    • addedOutput schema / properties / vote
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "Dynamic upstream JSON record.",
      +  "properties": {},
      +  "type": "object"
      +}
  3. 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": [
      +      "effectiveQuery",
      +      "totalCount"
      +    ]
      +  },
      +  {
      +    "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: `not_found`: A requested bill, member, committee, report, vote, or nomination does not exist in Congress.gov. `rate_limited`: The Congress.gov API rate limit (5,000 requests/hour per key) was exceeded. `invalid_request`: Congress.gov rejected the request as malformed — a bad date range or an identifier with an unexpected shape. `upstream_error`: Congress.gov returned an unexpected error (5xx or another non-2xx status). Other values are possible when a failure originates below the handler.",
      +          "examples": [
      +            "not_found",
      +            "rate_limited",
      +            "invalid_request",
      +            "upstream_error"
      +          ],
      +          "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: -[
      -  "effectiveQuery",
      -  "totalCount"
      -]
  4. Changed2 schema fields changed
    • addedInput schema / properties / chamber
      Added value: +{
      +  "default": "house",
      +  "description": "Chamber whose votes to query. 'house' (default) draws from the Congress.gov API; 'senate' draws from the Senate's official LIS roll-call feed. Roll call numbers reset each session and are specific to one chamber.",
      +  "enum": [
      +    "house",
      +    "senate"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / order / description
      Previous value: -"Sort order for 'list', by vote update date. 'recent' (default) returns newest first; 'oldest' returns ascending. With 'recent', offset=0 always returns the strictly newest page. Ignored by 'get' and 'members'."New value: +"Sort order for 'list'. 'recent' (default) returns newest first; 'oldest' returns ascending. House sorts by vote update date (with 'recent', offset=0 always returns the strictly newest page); Senate sorts by roll call number. Ignored by 'get' and 'members'."
  5. Changed6 schema fields changed
    • removedOutput schema / description
      Removed value: -"Detail-mode key 'vote' carries: Vote record for `get` and `members` (question, result, party totals, member positions); absent for `list`."
    • addedOutput schema / properties / effectiveQuery
      Added value: +{
      +  "description": "The browse scope and applied filters.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / notice
      Added value: +{
      +  "description": "Guidance when results are empty, a page is past the end, or a caveat applies.",
      +  "type": "string"
      +}
    • removedOutput schema / properties / query
      Removed value: -{
      -  "description": "Echo of the applied filters for list-mode queries. Rendered as the first line of the response.",
      -  "type": "string"
      -}
    • addedOutput schema / properties / totalCount
      Added value: +{
      +  "description": "Total results across all pages.",
      +  "type": "number"
      +}
    • addedOutput schema / required
      Added value: +[
      +  "effectiveQuery",
      +  "totalCount"
      +]
  6. Changed5 schema fields changed
    • changedInput schema / properties / order / description
      Previous value: -"Sort order for 'list' (sorts by update date). 'recent' (default) is newest first; 'oldest' is ascending. The upstream API ignores sort params on this endpoint, so 'recent' is implemented client-side by fetching the tail and reversing. Ignored by 'get' and 'members'."New value: +"Sort order for 'list', by vote update date. 'recent' (default) returns newest first; 'oldest' returns ascending. With 'recent', offset=0 always returns the strictly newest page. Ignored by 'get' and 'members'."
    • changedOutput schema / description
      Previous value: -"Vote data from Congress.gov API."New value: +"Detail-mode key 'vote' carries: Vote record for `get` and `members` (question, result, party totals, member positions); absent for `list`."
    • addedOutput schema / properties / data
      Added value: +{
      +  "description": "Result rows. Per-tool item shape is rendered in the markdown body.",
      +  "items": {
      +    "additionalProperties": {},
      +    "description": "Upstream JSON record. Per-tool item shape is rendered in the markdown body.",
      +    "properties": {},
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / pagination
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Pagination metadata: total count and next offset.",
      +  "properties": {
      +    "count": {
      +      "description": "Total result count across all pages.",
      +      "maximum": 9007199254740991,
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "nextOffset": {
      +      "anyOf": [
      +        {
      +          "maximum": 9007199254740991,
      +          "minimum": 0,
      +          "type": "integer"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "Offset to pass for the next page, or null when there are no more pages."
      +    }
      +  },
      +  "required": [
      +    "count"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / query
      Added value: +{
      +  "description": "Echo of the applied filters for list-mode queries. Rendered as the first line of the response.",
      +  "type": "string"
      +}
  7. Changed1 schema field changed
    • addedInput schema / properties / order
      Added value: +{
      +  "default": "recent",
      +  "description": "Sort order for 'list' (sorts by update date). 'recent' (default) is newest first; 'oldest' is ascending. The upstream API ignores sort params on this endpoint, so 'recent' is implemented client-side by fetching the tail and reversing. Ignored by 'get' and 'members'.",
      +  "enum": [
      +    "recent",
      +    "oldest"
      +  ],
      +  "type": "string"
      +}
  8. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.