Skip to main content
Glama
Sign In
regintel-mcp

regintel-mcp

by Black-Swan-Causal-Labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

search_dockets

Search regulations.gov dockets by keyword and filter by agency or docket type to retrieve docket IDs, titles, types, and modification dates.

Instructions

Search regulations.gov dockets by keyword. docket_type: 'Rulemaking' or 'Nonrulemaking' (FDA guidance dockets are Nonrulemaking). Returns docketId, title, docketType, lastModified.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_dockets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
agencyNoFDA
refreshNo
docket_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden, and it discloses only the returned fields. It says nothing about pagination behavior, result caps via limit, caching semantics behind the 'refresh' flag, or whether results are truncated — all material for an agent planning a call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, front-loaded with the search purpose followed by parameter and return detail. No filler, though the parenthetical about FDA guidance dockets is slightly awkwardly placed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequately covers the core query and docket_type semantics, but for a tool with no annotations, no output schema, and five undocumented parameters, the definition leaves out too much about caching, pagination, and agency scoping to be considered complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate; it partially does by explaining the keyword query and giving valid docket_type values with a domain hint that FDA guidance dockets are Nonrulemaking. However, limit, agency (default FDA), and refresh are left entirely unexplained, which is a significant gap for a 5-param tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search regulations.gov dockets by keyword'), which an agent can distinguish from the single-record sibling get_docket. It lacks an explicit note that it returns lists rather than one docket, but the purpose is otherwise unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: searching is the natural read path versus get_docket for a known docketId, but the description never names alternatives or conditions for choosing them. No guidance on when to broaden/narrow the query or when to use list_documents instead.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools