Skip to main content
Glama

Blackbook Protocol Advisor

by io.github.koynlabs

Get HMRC guidance

get_hmrc_guidance
Read-onlyIdempotent

Retrieve approved GOV.UK/HMRC trust and inheritance-tax guidance by topic. Returns a title, official URL, and short summary. Not a live scrape of GOV.UK.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicYesGuidance topic. Example: trs or inheritance tax
jurisdictionNoJurisdiction filter. Example: UK

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicYesTopic that was requested
guidanceYesApproved GOV.UK title, URL, and summary
jurisdictionYesJurisdiction used

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds useful context beyond the annotations: results are approved rather than live-scraped, and each result includes a title, official URL, and short summary.

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

Conciseness5/5

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

Two short sentences with no filler. The action and scope are front-loaded, and the live-scrape caveat is a single useful clause that earns its place.

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 one required parameter, one optional parameter, 100% schema coverage, an output schema, and read-only annotations, nothing essential is missing. The description also explains the return shape and data-source caveat clearly.

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 parameters are already documented. The phrase 'trust and inheritance-tax guidance' modestly reinforces the expected topic values, but the description does not add meaning for the optional jurisdiction filter beyond what the schema provides.

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 opens with a specific verb and resource: 'Retrieve approved GOV.UK/HMRC trust and inheritance-tax guidance by topic.' It clearly distinguishes the tool from siblings like get_companies_house_guidance, and the caveat 'Not a live scrape of GOV.UK' further differentiates its role.

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?

The description gives clear context: use this for approved/cached HMRC guidance on trust and inheritance tax, and explicitly rules out live scraping. However, it does not explicitly name an alternative tool or provide a when-not-to-use condition beyond the live-scrape exclusion.

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

All Blackbook Protocol Advisor toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation4/5

Each tool occupies a distinct step in the intake-to-submission pipeline, with clearly paired tools like prepare_submit_confirmation/confirm_and_submit. A few knowledge/checklist tools such as get_module_playbook, get_skill, and search_book could overlap at the margins, but their descriptions separate modules, workflow skills, and cited passages well enough.

Naming Consistency4/5

The set overwhelmingly follows lower_snake_case action_object naming like get_*, list_*, prepare_*, fill_fields, and open_portal. Minor deviations such as confirm_and_submit and wait_for_user_ready are still imperative and readable, so the naming remains predictable overall.

Tool Count3/5

At 25 tools, the server sits at the top of the 'heavy but borderline' range. The broad advisory/portal-automation scope mostly justifies the count, but several browser-session helpers and guidance/checklist tools could plausibly be consolidated without losing core capability.

Completeness4/5

The tool surface covers the full workflow: intake, risk assessment, guidance, module/skill selection, drafting and review bundles, self-serve or assisted browsing, form filling, and guarded submission. Minor gaps like updating intake data or checking post-submission status are workable rather than fatal.

Resources