Skip to main content
Glama

Hmrc Manual Changes

hmrc_manual_changes
Read-onlyIdempotent

Read what HMRC most recently changed in one of its internal manuals, the per-section revision log the department publishes with each manual, newest first. Each entry carries the section id and title, HMRC's own note of what changed ("Updated for change in legislation for intermediaries", "Page withdrawn"), its published_at and age_days. Use it to tell whether HMRC's stated position on a topic has moved, to audit a manual's freshness, or to watch a specific area of UK tax guidance for revisions.

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": {
      "limit": 5,
      "manual": "employment-income-manual"
    },
    "name": "hmrc_manual_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoChange entries to return, 1-200 (default 25).
sinceNoOnly changes published on or after this date (YYYY-MM-DD).
manualYesManual base_path or slug, e.g. "employment-income-manual" or "/hmrc-internal-manuals/capital-gains-manual".
section_idNoOnly changes to this section, e.g. "EIM42750".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. Beyond that, the description adds genuine context: newest-first ordering, and the exact shape of each entry (section id, title, HMRC's own change note with examples, published_at, age_days). It does not mention pagination limits or rate behavior, which keeps it below a 5.

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?

Two sentences, front-loaded with the core action and followed by the return-field inventory. Dense but every clause carries information; the parenthetical change-note examples earn their place by showing what the notes look like.

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?

There is no output schema, and the description compensates by enumerating the returned fields and their semantics, plus ordering. Combined with full schema coverage on inputs and covering annotations, an agent has everything needed to call it correctly and interpret results.

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%, with limit, since, manual and section_id all documented including formats and an example. The description adds no parameter-level meaning beyond the schema, so the baseline of 3 is appropriate.

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?

The description states a specific verb and resource ('Read what HMRC most recently changed in one of its internal manuals') and clarifies the nature of the data as a per-section revision log ordered newest first. It is clear what the tool returns, though it never names or contrasts against the obvious siblings (hmrc_manual_search, hmrc_manual_section, recent_changes), leaving differentiation implicit.

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?

It gives three concrete use cases: detecting whether HMRC's position on a topic has moved, auditing a manual's freshness, and watching a specific area of UK tax guidance. That is clear when-to-use guidance, but there are no explicit exclusions or pointers to alternative tools for related needs such as full-text search or fetching a section body.

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.