Skip to main content
Glama

Mhra Recent Changes

mhra_recent_changes
Read-onlyIdempotent

MHRA documents added or revised since a date, newest first, the weekly-refresh feed. Pass an ISO date such as "2026-09-01". Returns the same rows as mhra_search plus the cutoff that was applied, so replaying the same since gives the same answer. NOTE what the register can and cannot tell you: a new or revised DOCUMENT is what is recorded here. A withdrawal is not published as an event, so this cannot report withdrawals, treat it as "new and changed", not "new, changed and withdrawn".

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "since": "2026-09-01"
    },
    "name": "mhra_recent_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum documents to return, 1-200 (default 50).
sinceYesISO date or datetime, e.g. "2026-09-01" or "2026-09-01T00:00:00Z".
doc_typeNoRestrict to "Spc", "Pil" or "Par".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, open-world behavior, but the description adds ordering (newest first), refresh cadence (weekly), and replay determinism for identical `since` values. Most valuably, it discloses a data-coverage limitation — that withdrawals are never published as events — which an agent could not infer from any structured field.

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?

Front-loaded with the core purpose and the date-passing instruction before the caveat. The closing NOTE costs some length and repeats the same idea in two phrasings, but it earns its place by preventing a real misreading of results.

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

Completeness5/5

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

With no output schema, the description still tells the agent what comes back ('the same rows as mhra_search plus the cutoff') and how it is ordered. Combined with the explicit limitation on withdrawals, an agent has everything needed to call and interpret this tool correctly.

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% and the schema already provides an ISO date example, a limit range, and the doc_type values, so the description's date guidance is largely redundant. Baseline 3 applies since the schema carries the parameter burden.

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 ('MHRA documents added or revised since a date'), plus ordering ('newest first') and the nature of the feed ('weekly-refresh'). It also positions itself against the sibling mhra_search by describing the delta: 'same rows as mhra_search plus the cutoff that was applied'.

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 clear operating context: pass an ISO date, results are deterministic for a given `since`, and explicitly warns about the boundary case that withdrawals are not events, so the tool should be read as 'new and changed', not 'new, changed and withdrawn'. It does not give an explicit rule for when to prefer mhra_search over this feed, which keeps it short of a 5.

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.