Skip to main content
Glama

Hmrc Manuals

hmrc_manuals
Read-onlyIdempotent

List HM Revenue & Customs internal manuals and other UK departmental manuals, the guidance HMRC caseworkers and other officials actually apply, published in full. Covers income tax, PAYE, employment income, capital gains, corporation tax, VAT, inheritance tax, pensions, stamp duty, national insurance, trusts, residence and domicile, double taxation, compliance and penalties, plus non-HMRC manuals from other departments. Use this to see what manuals exist and their base_paths, then hmrc_manual_search to find the section that answers a question.

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": {
      "count": 5,
      "query": "capital gains"
    },
    "name": "hmrc_manuals"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoManuals per page, 1-100 (default 50).
queryNoOptional free text to narrow the manual list, e.g. "capital gains" or "pensions".
startNoOffset for paging.
include_other_departmentsNoAlso return non-HMRC departmental manuals (Home Office, DWP, and others). Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety behaviour needs no restating. The description adds useful context that the annotations do not cover: the material is 'published in full' and the result gives base_paths that feed a follow-up search. Pagination behaviour is left to the schema, which is acceptable given the coverage there.

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?

The listing action and the routing to hmrc_manual_search frame the description, and the opening sentence comes first. The long list of tax topics is bulky, but it does convey coverage, which helps an agent judge whether to route a question here; overall the description is slightly over-long.

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

Completeness4/5

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

All parameters are documented in the schema, the annotations cover the safety profile, and no output schema exists, so the description carries the burden of explaining what comes back; it partly does so by naming base_paths. Combined, the result is sufficiently complete for a four-parameter listing tool, with only minor gaps in paging and return details.

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 the schema already defines count, start, query and include_other_departments, and a baseline of 3 is appropriate. The description reinforces the meaning of include_other_departments by naming departmental manuals, but it adds no syntax, format or filtering semantics beyond what the schema states.

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?

The description uses a specific verb and resource ('List HM Revenue & Customs internal manuals') and states the scope clearly: it lists which manuals exist and gives their base_paths. It distinguishes the tool's role from the sibling hmrc_manual_search, so an agent can tell the two apart without opening either schema.

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 explicit when-to-use guidance: 'Use this to see what manuals exist and their base_paths, then hmrc_manual_search to find the section that answers a question.' That is a clear two-step workflow with a named alternative. It does not mention hmrc_manual_section or hmrc_manual_changes, and it gives no guidance on when to enable include_other_departments, so the guidance is strong but not complete.

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.