get_membersGet current members of Congress with their name, party, state, district (for representatives), and contact information.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Number of results to return (default: 50, max: 600) |
| Name | Required | Description | Default |
|---|---|---|---|
| total | Yes | Total current members of Congress | |
| members | Yes | ||
| returned | Yes | Number of members returned |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / examplesAdded value: +[
+ {
+ "limit": 50
+ }
+]Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "members": {
+ "items": {
+ "properties": {
+ "birthday": {
+ "description": "Birth date",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "district": {
+ "description": "Congressional district (for representatives)",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "enddate": {
+ "description": "Role end date",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "gender": {
+ "description": "Gender",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "link": {
+ "description": "GovTrack member URL",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "name": {
+ "description": "Member full name",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "party": {
+ "description": "Political party",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "person_id": {
+ "description": "Person ID",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "role_id": {
+ "description": "Role ID",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "role_type": {
+ "description": "Role type (senator or representative)",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "sortname": {
+ "description": "Member name in sort format",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "startdate": {
+ "description": "Role start date",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "state": {
+ "description": "State code",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "state_name": {
+ "description": "State name",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "title": {
+ "description": "Official title",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "returned": {
+ "description": "Number of members returned",
+ "type": "number"
+ },
+ "total": {
+ "description": "Total current members of Congress",
+ "type": "number"
+ }
+ },
+ "required": [
+ "total",
+ "returned",
+ "members"
+ ],
+ "type": "object"
+}Input schema / examplesRemoved value: -[
- {
- "_apiKey": "your-propublica-congress-api-key",
- "chamber": "senate",
- "congress": 118
- },
- {
- "_apiKey": "your-propublica-congress-api-key",
- "chamber": "house"
- }
-]Output schema / (root)Previous value: -{
- "properties": {
- "chamber": {
- "description": "Chamber (senate or house)",
- "type": "string"
- },
- "congress": {
- "description": "Congress number",
- "type": "number"
- },
- "count": {
- "description": "Number of members returned",
- "type": "number"
- },
- "members": {
- "description": "List of members",
- "items": {
- "properties": {
- "district": {
- "description": "Congressional district",
- "type": [
- "string",
- "null"
- ]
- },
- "gender": {
- "description": "Gender",
- "type": [
- "string",
- "null"
- ]
- },
- "id": {
- "description": "Member ID",
- "type": [
- "string",
- "null"
- ]
- },
- "in_office": {
- "description": "Currently in office",
- "type": [
- "boolean",
- "null"
- ]
- },
- "missed_votes_pct": {
- "description": "Percentage of votes missed",
- "type": [
- "number",
- "null"
- ]
- },
- "name": {
- "description": "Full name",
- "type": [
- "string",
- "null"
- ]
- },
- "next_election": {
- "description": "Next election year",
- "type": [
- "string",
- "null"
- ]
- },
- "party": {
- "description": "Political party",
- "type": [
- "string",
- "null"
- ]
- },
- "phone": {
- "description": "Phone number",
- "type": [
- "string",
- "null"
- ]
- },
- "state": {
- "description": "State abbreviation",
- "type": [
- "string",
- "null"
- ]
- },
- "title": {
- "description": "Short title (Senator, Representative)",
- "type": [
- "string",
- "null"
- ]
- },
- "twitter": {
- "description": "Twitter account handle",
- "type": [
- "string",
- "null"
- ]
- },
- "url": {
- "description": "Official URL",
- "type": [
- "string",
- "null"
- ]
- },
- "votes_with_party_pct": {
- "description": "Percentage of votes with party",
- "type": [
- "number",
- "null"
- ]
- }
- },
- "type": "object"
- },
- "type": "array"
- }
- },
- "required": [
- "congress",
- "chamber",
- "count",
- "members"
- ],
- "type": "object"
-}New value: +nullOutput schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "chamber": {
+ "description": "Chamber (senate or house)",
+ "type": "string"
+ },
+ "congress": {
+ "description": "Congress number",
+ "type": "number"
+ },
+ "count": {
+ "description": "Number of members returned",
+ "type": "number"
+ },
+ "members": {
+ "description": "List of members",
+ "items": {
+ "properties": {
+ "district": {
+ "description": "Congressional district",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "gender": {
+ "description": "Gender",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "id": {
+ "description": "Member ID",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "in_office": {
+ "description": "Currently in office",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "missed_votes_pct": {
+ "description": "Percentage of votes missed",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "name": {
+ "description": "Full name",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "next_election": {
+ "description": "Next election year",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "party": {
+ "description": "Political party",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "phone": {
+ "description": "Phone number",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "state": {
+ "description": "State abbreviation",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "title": {
+ "description": "Short title (Senator, Representative)",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "twitter": {
+ "description": "Twitter account handle",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "url": {
+ "description": "Official URL",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "votes_with_party_pct": {
+ "description": "Percentage of votes with party",
+ "type": [
+ "number",
+ "null"
+ ]
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "congress",
+ "chamber",
+ "count",
+ "members"
+ ],
+ "type": "object"
+}Input schema / examplesAdded value: +[
+ {
+ "_apiKey": "your-propublica-congress-api-key",
+ "chamber": "senate",
+ "congress": 118
+ },
+ {
+ "_apiKey": "your-propublica-congress-api-key",
+ "chamber": "house"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint as true/false appropriately, indicating a safe, read-only operation. The description adds no extra behavioral detail but does not contradict annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, succinct sentence that front-loads the purpose and key details. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simplicity of the tool (single optional parameter, output schema present), the description completely covers what the tool does and its output fields. No gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has full coverage (100%) for the limit parameter with a description. The tool's description does not add additional meaning beyond the schema, meeting the baseline of 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'get' and the resource 'current members of Congress', and lists the output fields (name, party, state, district, contact information). This distinguishes it from sibling tools like get_bill or get_votes.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for retrieving current member details, but does not explicitly mention when not to use it or provide alternative tools. However, given the simplicity and the context of sibling tools, it is clear enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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.
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.
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.
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.