recent_regulatory_changesList the most recent regulatory publications across all covered regulators, newest first. Use when asked what is new, what happened this week, or for a general catch up rather than a specific topic.
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | Look back this many days. | |
| limit | No | Maximum records to return. | |
| jurisdiction | No | Restrict to one jurisdiction. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds behavioral context beyond the readOnlyHint annotation: it mentions ordering ('newest first'), scope ('all covered regulators'), and usage context ('general catch up'). It does not contradict annotations and provides sufficient transparency for safe usage.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise: two sentences with no wasted words. The first sentence states the core function, and the second provides usage guidance. Front-loaded and efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers purpose, usage timing, ordering, and scope. It lacks explicit mention of the output format (e.g., fields returned), but given the simplicity of the tool and rich schema, it is nearly complete for an AI to decide invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so parameters are well-described in the schema (days, limit, jurisdiction with defaults and ranges). The description does not add significant new parameter semantics beyond the schema, earning a baseline score of 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('list'), the resource ('most recent regulatory publications'), and the scope ('across all covered regulators, newest first'). It also includes an example usage pattern, distinguishing it from siblings like search_regulatory_changes for specific topics.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly states when to use the tool: 'when asked what is new, what happened this week, or for a general catch up rather than a specific topic.' This provides clear context but does not explicitly exclude alternatives like get_regulatory_change or list_coverage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: retrieving a single full record, listing monitored regulators, listing recent publications, and searching by topic/date. No overlap exists.
All tool names follow a consistent verb_noun snake_case pattern (get_regulatory_change, list_coverage, recent_regulatory_changes, search_regulatory_changes).
With only 4 tools, the server is well-scoped for the domain of regulatory change monitoring. Each tool serves a distinct and necessary function without excess.
The tool set covers core operations: retrieving full records with history, listing coverage, viewing recent changes, and searching. Minor gap: search lacks an explicit regulator filter, but coverage list provides context.