Clearon Legislation Monitor MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_server_healthB | Report monitor state and safety boundaries. |
| list_jurisdictionsC | List official source routes for all states and supported local jurisdictions. |
| scan_official_sourceB | Retrieve one explicit public official-source URL and return keyword matches and candidate links. Results are leads, not verification. |
| search_openstates_billsA | Search Open States v3 for discovery leads. Results never count as final verification and must be pivoted back to official sources before watchlist acceptance. |
| search_nyc_legistar_mattersB | Search the official NYC Legistar matters API for discovery leads. Results must still be verified against the official matter page or enacted local law before watchlist acceptance. |
| record_discovery_candidateA | Record a deduplicated candidate with an official measure URL for human review; does not add it to the watchlist. |
| list_discovery_candidatesB | List candidates by review status. |
| review_candidateA | Explicitly accept or reject a candidate. Acceptance requires a normalized watch entry and is the only candidate-to-watchlist path. |
| import_normalized_watchlistC | Idempotently seed the MCP from the workspace normalized watchlist CSV. |
| list_watchlistC | List all or active monitored measures. |
| record_measure_observationB | Record an official-source observation, compute material field changes, and update the watch snapshot. Does not publish. |
| dedupe_watchlist_measuresA | Remove duplicate watchlist rows while preserving append-only audit history and migrating any stored observations to the survivor measure. |
| record_exceptionA | Record a retrieval, parsing, migration, or verification exception without treating it as a legal-status change. |
| resolve_exceptionA | Mark a previously recorded exception as resolved after a successful re-check or remediation. |
| get_due_reviewsC | List active measures whose next-review date is due. |
| get_exceptionsB | List consolidated exceptions, optionally since an ISO datetime. |
| verify_event_logA | Replay the append-only event log and compare it with the stored snapshot. |
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 17 tools
Each tool is scoped to a distinct workflow stage or data type: discovery candidates, watchlist measures, exceptions, health, and audit. Search tools are source-specific, and state/verification boundaries are clearly described, so an agent should rarely select the wrong tool.
All tool names are snake_case verb_noun and generally predictable. Minor inconsistency exists between list_* and get_* for similar collection-style operations, but the pattern is still coherent and readable.
Seventeen tools is on the heavier side, but the count is justified by the broad legislation-monitoring workflow: discovery, candidate review, watchlist management, observations, exceptions, and audit. The scope feels intentional rather than padded.
The server covers the major lifecycle stages from discovery through watchlist observation and exception handling, with strong audit support. Minor gaps exist, such as no explicit watchlist removal/deactivation tool and no publish step despite observations being non-publishing.