Skip to main content
Glama

Congress

by io.github.pipeworx-io

Get Bill

get_bill
Read-onlyIdempotent

Get full details for a congressional bill by its ID. Returns text, sponsors, cosponsors, committee assignments, actions, and vote history.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesGovTrack bill ID (numeric)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesBill ID
linkNoGovTrack bill URL
titleNoFull bill title
numberNoBill number
statusNoCurrent status code
congressNoCongress number
bill_typeNoBill type code
status_dateNoDate of current status
sponsor_nameNoPrimary sponsor name
status_labelNoCurrent status label
bill_type_labelNoBill type label
introduced_dateNoBill introduction date
title_without_numberNoBill title without number prefix

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "id": 3456789
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "bill_type": {
+      "description": "Bill type code",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "bill_type_label": {
+      "description": "Bill type label",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "congress": {
+      "description": "Congress number",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "id": {
+      "description": "Bill ID",
+      "type": "number"
+    },
+    "introduced_date": {
+      "description": "Bill introduction date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "link": {
+      "description": "GovTrack bill URL",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "number": {
+      "description": "Bill number",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "sponsor_name": {
+      "description": "Primary sponsor name",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "status": {
+      "description": "Current status code",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "status_date": {
+      "description": "Date of current status",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "status_label": {
+      "description": "Current status label",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "title": {
+      "description": "Full bill title",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "title_without_number": {
+      "description": "Bill title without number prefix",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "id"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • removedInput schema / examples
      Removed value: -[
-  {
-    "id": 3456789
-  }
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "bill_type": {
-      "description": "Bill type code",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "bill_type_label": {
-      "description": "Bill type label",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "congress": {
-      "description": "Congress number",
-      "type": [
-        "number",
-        "null"
-      ]
-    },
-    "id": {
-      "description": "Bill ID",
-      "type": "number"
-    },
-    "introduced_date": {
-      "description": "Bill introduction date",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "link": {
-      "description": "GovTrack bill URL",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "number": {
-      "description": "Bill number",
-      "type": [
-        "number",
-        "null"
-      ]
-    },
-    "sponsor_name": {
-      "description": "Primary sponsor name",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "status": {
-      "description": "Current status code",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "status_date": {
-      "description": "Date of current status",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "status_label": {
-      "description": "Current status label",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "title": {
-      "description": "Full bill title",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "title_without_number": {
-      "description": "Bill title without number prefix",
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "required": [
-    "id"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "bill_type": {
+      "description": "Bill type code",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "bill_type_label": {
+      "description": "Bill type label",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "congress": {
+      "description": "Congress number",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "id": {
+      "description": "Bill ID",
+      "type": "number"
+    },
+    "introduced_date": {
+      "description": "Bill introduction date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "link": {
+      "description": "GovTrack bill URL",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "number": {
+      "description": "Bill number",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "sponsor_name": {
+      "description": "Primary sponsor name",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "status": {
+      "description": "Current status code",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "status_date": {
+      "description": "Date of current status",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "status_label": {
+      "description": "Current status label",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "title": {
+      "description": "Full bill title",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "title_without_number": {
+      "description": "Bill title without number prefix",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "id"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "id": 3456789
+  }
+]
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already provide readOnlyHint, idempotentHint, etc. Description adds valuable context by enumerating the specific data fields returned, beyond what annotations convey.

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 fluff, first sentence states core purpose. Efficient and well-structured.

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?

Given the simple one-parameter input, presence of output schema, and comprehensive annotations, the description covers all necessary context. Returns list is sufficiently detailed.

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 coverage is 100% and describes the parameter. Description does not add additional semantic information beyond the schema's 'GovTrack bill ID (numeric)'.

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?

Clearly states the tool retrieves full details for a congressional bill by ID. Lists specific data returned (text, sponsors, cosponsors, committee assignments, actions, vote history), distinguishing it from sibling tools like search_bills or get_recent_bills.

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?

Implies usage when you have a bill ID and need comprehensive details. Does not explicitly state when not to use or name alternatives, but context with siblings provides some differentiation.

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

All Congress toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation2/5

Multiple tools occupy the same functional space: ask_pipeworx, ask_pipeworx_beta, ask_ipeworx_grounded, and deep_research all answer questions; disover_tools, suggest_questions, and pipeworx_trending all serve discovery; and five polymarket_* tools plus bet_research overlap heavily on prediction-market opportunity detection. The descriptions are detailed, but the boundaries are subtle enough that an agent can easily pick the wrong tool.

Naming Consistency4/5

The set is uniformly lowercase snake_case and uses recognizable prefixes such as ask_pipeworx, polymarket_, pipeworx_, and get_, which makes the naming fairly predictable. It is not a strict verb_noun convention — some names are noun phrases like entity_profile or ai_visility_check — but the overall style is consistent.

Tool Count2/5

With 36 tools, the surface is far heavier than the 'Congress' name suggests: only five tools are actually about congressional data, while the rest are general research, memory, subscription, and meta utilities. Many of these overlap, so the count feels bloated rather than well-scoped.

Completeness3/5

For Congress-specific work, the core needs are covered: search bills, get bill details, list members, and retrieve recent votes. However, deeper legislative operations like member voting records, committee actions, and amendments are missing, and the surrounding Pipeworx tools do nothing to close that gap. As a general data-research platform it is broad, but its actual 'Congress' identity feels incompletely realized.

Resources