pr-legislative-x402
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PR_X402_API_BASE | No | URL of the underlying HTTP API | http://localhost:4021 |
| WALLET_PRIVATE_KEY | No | Private key for auto-paying (optional) |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_pr_legislationA | Search measures (proyectos y resoluciones) of the Puerto Rico Legislative Assembly by text, chamber, or status. Returns summary rows. |
| get_pr_billA | Get full detail for one Puerto Rico legislative measure by identifier: abstract, sponsors, and action history. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one searches for legislation with filters, the other retrieves full details for a specific measure. There is no overlap or ambiguity.
Both tools follow a verb_noun pattern, but one uses 'pr_bill' and the other 'pr_legislation,' which is a minor inconsistency in resource naming. Overall style is consistent and readable.
With only two tools, the set feels thin for a legislative domain, though it may be sufficient for a minimal read-only API. The count is borderline but not unreasonable.
The tool surface covers search and detail retrieval, which are the core operations for accessing legislative measures. No significant gaps are apparent, though more specialized endpoints (e.g., by chamber or session) could be added.