Skip to main content
Glama

regulatory-change-brief

Regulatory Change Brief (Federal Register, EDGAR, Dockets) — Given an industry or topic and optional agencies, CFR parts, terms and companies, pulls recent US regulatory changes from official free sources: Federal Register final and proposed rules (with effective dates, comment deadlines and official URLs), SEC EDGAR 8-K items and other filings for named companies, and CourtListener dockets and opinions when the operator has a token. Days remaining are comp

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": "regulatory-change-brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
focusNoWeights ranking and the impact assessment toward operations, reporting or enforcement.
termsNoFederal Register search phrases, e.g. "data breach notification".
agenciesNoAgency names, acronyms or Federal Register slugs, e.g. "SEC", "Environmental Protection Agency".
industryNoIndustry or topic, e.g. "community banks offering consumer credit". Used to plan searches and to judge impact.
cfr_partsNoCFR parts, e.g. "17 CFR 240" or "40 CFR 60".
companiesNoCompany names, tickers or CIKs whose recent SEC filings (8-K items, 10-K/Q) to list.
sic_codesNoSIC codes; industry context only, registrants are not enumerated by SIC.
window_daysNoPublication window ending today, 1 to 180 days (default 30). Proposed rules published earlier whose comment period is still open are also included.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden. It does usefully disclose that sources are official and free, that CourtListener results only appear 'when the operator has a token' (an auth dependency callers must know about), and that rules carry effective dates and comment deadlines. It omits rate limits, failure behavior, and the actual return shape, and the final sentence is cut off mid-word ('Days remaining are comp'), so a key ranking/scoring behavior is never disclosed.

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

Conciseness3/5

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

The purpose is front-loaded in a single dense sentence with no filler, which is good. However the text terminates mid-sentence ('Days remaining are comp'), leaving an incomplete clause and an unpolished definition. It is one run-on sentence rather than a structured brief, making the source list harder to scan.

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?

Eight optional parameters, no annotations, and no output schema mean the description must cover both behavior and return values. It never describes what a result contains or how results are ordered/ranked (the truncated 'Days remaining are comp' sentence was presumably where ranking was explained). For a multi-source aggregation tool of this complexity, the definition leaves the agent unable to predict the response.

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 every one of the 8 parameters is already documented, including the focus enum and the window_days default. The description adds only that search planning and impact judgment derive from 'industry', which is marginal value over the schema. Baseline 3 applies when the schema does the heavy lifting.

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 set — pulls recent US regulatory changes from Federal Register rules, SEC EDGAR filings and CourtListener dockets — scoped by industry/topic. An agent can tell what it produces and roughly from which sources. It does not differentiate itself from any sibling (form-finder, precedent-search, legal-cite-verifier) or state why one would pick this over a general search, so it stops short of a 5.

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 implied by the phrasing 'Given an industry or topic and optional agencies, CFR parts, terms and companies', which conveys the intended entry point. There is no explicit when-to-use vs when-not guidance, no statement of what this tool is a poor fit for, and no named alternative among the legal-research siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources