regintel-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REGULATIONS_GOV_API_KEY | Yes | Your Regulations.gov API key, sent only as the X-Api-Key header. Get a free key at https://open.gsa.gov/api/regulationsgov/ and put it in .env. DEMO_KEY can be used for single lookups but is too rate-limited for full corpus pulls. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_docketsB | Search regulations.gov dockets by keyword. docket_type: 'Rulemaking' or 'Nonrulemaking' (FDA guidance dockets are Nonrulemaking). Returns docketId, title, docketType, lastModified. |
| get_docketC | Docket metadata plus the total number of public comments (e.g. 'FDA-2020-D-2307'). |
| list_documentsB | Documents in a docket (Federal Register notices, draft/final guidance, meeting material) with documentType, subtype, postedDate and every downloadable file URL. Use it to locate the draft guidance, the final guidance, and the notices of availability. |
| list_commentsB | All public comments in a docket (pagination handled). Each row: commentId, title, postedDate, submitterName, and — once build_corpus has run — has_attachment, is_stub (body < 50 chars and no attachment) and duplicate_of (same submitter, near-identical text). Flags never drop rows. |
| get_commentB | One comment in full: body text, submitter fields (organization, name, category, location), attachment metadata and extracted attachment text. max_chars truncates long texts. |
| build_corpusA | Pull every comment and attachment of a docket into the local cache and extract attachment text. Resumable: anything already cached is skipped, so re-running finishes an interrupted pull. max_comments caps new detail fetches per call. Returns counts of comments, attachments, extraction outcomes, OCR needs, stubs, duplicate groups and itemised failures. |
| get_guidance_textC | Plain text of a guidance document, split into sections by its numbered headings (I./A./1.). ref is a regulations.gov document id (e.g. 'FDA-2020-D-2307-0002') or a URL (an fda.gov guidance page or a /media//download PDF). |
| diff_guidanceA | Section-aligned draft-vs-final diff. For each section: section_id, heading, status (added/removed/modified/unchanged), draft_text, final_text, paragraph_changes (incl. paragraphs moved between sections) and change_summary_stats. Refs as in get_guidance_text. write_to saves the full diff as JSON (relative paths resolve to the repo) and returns a summary. |
| export_corpusB | Write the cached corpus as JSONL (one full comment per line, with stub/duplicate flags) to output//corpus.jsonl, for skills and subagents to read in batches. |
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 9 tools
Most tools have clear, distinct roles: search vs. get docket, list vs. get comment, list_documents vs. get_guidance_text, and diff_guidance are all separable. The only mild overlap is among the corpus trio (list_comments, build_corpus, export_corpus), which all touch comment data, though descriptions distinguish listing rows vs. populating cache vs. writing JSONL.
Consistent snake_case verb_noun pattern throughout: search_dockets, get_docket, list_documents, get_comment, list_comments, build_corpus, get_guidance_text, diff_guidance, export_corpus. Verbs (search/get/list/build/diff/export) map predictably to actions, and 'diff' is used as a clear verb form.
Nine tools sit comfortably in the well-scoped 3-15 range, and each covers a distinct step in the regulations.gov workflow (search, metadata, documents, comments, corpus build/export, guidance text/diff). No obviously redundant or filler tools.
Strong lifecycle coverage for docket exploration, comment collection, and guidance comparison, including caching and export. Minor gaps exist: there is no general document full-text fetch for non-guidance documents (e.g., Federal Register notices) beyond list_documents' file URLs, and no comment filtering/search by submitter or keyword.