Skip to main content
Glama

get_recent_regulations

Retrieve recently published Federal Register documents, up to a specified limit, to monitor new US regulations and agency actions.

Instructions

Get the most recently published Federal Register documents

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_recent_regulations"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of results to return (max 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/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 behavioral burden. It doesn't state sort order (presumably newest first), whether the 50-item cap is a hard truncation, or whether results are metadata-only or include full text. Only the read-only nature is inferable from the verb 'Get.'

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?

One front-loaded sentence with no filler or redundancy. It is efficient, though the brevity comes at the cost of the guidance and behavior noted above.

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

Completeness2/5

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

There is no output schema and no annotations, so the description must explain both what is returned and how results are ordered. It says neither, leaving an agent unsure whether items are full documents or summaries, or whether the list is sorted by publication date.

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%: the sole 'limit' parameter is documented with a default of 20 and a range of 1 to 50. The description adds no meaning beyond that, so the baseline of 3 applies.

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?

A specific verb plus resource: 'Get the most recently published Federal Register documents.' An agent can tell this is a recency-ordered listing of Federal Register documents rather than a keyword search. It never names the sibling 'search_federal_register,' however, so the boundary is left implicit.

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

Usage Guidelines2/5

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

The description says nothing about when to use this tool rather than 'search_federal_register' or 'get_recent_regulator_news.' The word 'recent' hints at browsing new publications, but no conditions, exclusions, or alternatives are stated.

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