cdgmcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CDG_GRAPHQL_ENDPOINT | No | The GraphQL endpoint URL for the Congress.gov-style legislative API. | http://dotnet10-dev:5208/graphql/ |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_billsA | Search and list bills/resolutions with flexible filters. Use this for questions like 'bills recently introduced in the House', 'bills that became law recently' (latestActionContains: 'Became Public Law'), or 'bills that passed the Senate' (latestActionContains: 'Passed Senate'). Results are paginated; increase 'limit' (max 50) for more. |
| get_billA | Fetch a single bill's full details. Identify it either by cdgId or by the combination of congress + billType + number. Optionally include related actions, cosponsors, committee activities, titles and text versions. |
| search_committee_activitiesA | Find committee activities (e.g. referrals) and the bills they relate to. Use this for questions like 'bills referred to the Commerce Committee recently' (committeeNameContains: 'Commerce', activityNameContains: 'Referred'). Each result includes the related bill summary. |
| search_actionsA | Search the legislative action history across bills. Use this to find events like 'Passed House', 'Passed Senate', 'Became Public Law', or to inspect actions by type/code. Each result includes the related bill. |
| search_cosponsorsA | Search bill cosponsorship records across bills. Useful for finding all the bills a member has cosponsored, or analysing cosponsorship by state/party. To get the cosponsors of a specific bill, prefer get_bill with includeCosponsors: true. |
| get_nodeA | Fetch any object directly by its Relay global |
| graphql_queryA | Execute an arbitrary read-only GraphQL query against the legislative API. Use this for complex questions the specialised tools do not cover (e.g. cross-referencing committee activities with bill cosponsors). Read the 'cdg://schema' resource for the full schema. Mutations are rejected. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| schema | The full GraphQL schema for the legislative API in SDL format, fetched live. |
| guide | How the legislative data is structured and how to answer common questions. |
| endpoint | The GraphQL endpoint this server is connected to. |
TDQS
Scored across 7 tools
Each tool targets a distinct entity or operation: bill lookup, generic node fetch, arbitrary GraphQL queries, and searches for actions, bills, committees, and cosponsors. No two tools have overlapping purposes.
Most tools follow a clear verb_noun pattern (e.g., get_bill, search_actions), but graphql_query breaks this by using a noun_noun format. Overall naming is still consistent and predictable.
Seven tools is well-scoped for the legislative domain, covering core entities (bills, actions, committees, cosponsors) plus a generic query tool. Not too many or too few.
The tool set covers bill retrieval, search, and relational data (actions, committees, cosponsors). The graphql_query tool fills any gaps, making the surface effectively complete for read-only legislative data access.