Regulatory Intel MCP

Recent Documents

recent_documents

Read-onlyIdempotent

List the most recent Federal Register documents, optionally filtered by type and issuing agency, over a look-back window. Use this to monitor newly published rules/notices from an agency.

Input Schema

TableJSON Schema

Name	Required	Description
`days`	No	Look back this many days (default 7, max 90).
`type`	No	Document type. One of: rule, proposed_rule, notice, presidential_document.
`agency`	No	Agency slug (from the 'agencies' tool).
`per_page`	No	Results to return (default 15, max 30).

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No
`count`	No
`since`	No
`source`	No
`results`	No
`provenance`	No	Where this answer came from. served_at is when Datakoot answered (UTC); upstream lists the official sources consulted. Datakoot may serve a briefly cached copy, so the source's own observation can be older than served_at.
`total_pages`	No
`window_days`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 8, 2026

addedOutput schema / properties / provenance

Added value: +{
+  "description": "Where this answer came from. served_at is when Datakoot answered (UTC); upstream lists the official sources consulted. Datakoot may serve a briefly cached copy, so the source's own observation can be older than served_at.",
+  "properties": {
+    "may_be_cached": {
+      "type": "boolean"
+    },
+    "publisher": {
+      "type": "string"
+    },
+    "served_at": {
+      "format": "date-time",
+      "type": "string"
+    },
+    "upstream": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedOct 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "count": {},
+    "note": {},
+    "results": {},
+    "since": {},
+    "source": {},
+    "total_pages": {},
+    "window_days": {}
+  },
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so safety and mutability are fully covered by structured data. The description adds only the look-back-window behavior, which is already restated in the schema, and says nothing about pagination limits or result ordering nuances.

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

Conciseness5/5

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

Two sentences, zero filler, with the core action and scope front-loaded before the use-case hint. Every clause earns its place.

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

Completeness4/5

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

An output schema exists, so return formatting need not be explained, and annotations cover the safety profile. What remains thin is pagination behavior and result ordering, but for a simple filtered-list tool the description is close to 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 description coverage is 100%, so all four parameters (days, type, agency, per_page) are already documented with defaults, max values, and an enum. The description's mention of type/agency filtering and the look-back window merely mirrors the schema rather than extending it (e.g., no guidance on agency slug format beyond a pointer to a sibling tool that the schema already provides).

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

Purpose5/5

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

States a specific verb and resource ('List the most recent Federal Register documents') plus the scoping mechanism ('over a look-back window') and optional filters. The recency framing implicitly separates it from the sibling search_documents, so an agent can route between them without opening schemas.

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

Usage Guidelines4/5

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

Gives a clear intended use case: monitoring newly published rules/notices from an agency. However, it never explicitly names search_documents as the alternative or states when to prefer full-text search over this recency listing, so the when-not guidance is absent.

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

All Regulatory Intel MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.