Skip to main content
Glama

Nice Guidance

nice_guidance
Read-onlyIdempotent

The published record for one piece of NICE guidance by reference number (TA1040, NG101, CG81, QS12, IPG123, DG55, HST20): title, programme, publication and last-review dates, overview, the chapters it contains, the condition area it sits under, and, the part that matters clinically, whether it is still current or has been withdrawn, terminated or replaced, naming the guidance that replaced it.

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": {
      "id": "TA1040"
    },
    "name": "nice_guidance"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesNICE reference number, e.g. "TA1040"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety is covered. The description adds real behavioral context beyond them: the record includes currency status (current, withdrawn, terminated, replaced) and names any replacing guidance, which is the clinically decisive signal. It omits what occurs when the reference does not exist.

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?

It is a single front-loaded sentence that puts the resource and identifier type first and the clinically important status detail last, where it lands as emphasis. It is slightly run-on but every clause carries information.

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?

With one required parameter, no nested objects and no output schema, the description does the work of explaining the return payload: title, programme, dates, overview, chapters, condition area and status. The only meaningful gap is failure behavior for an unrecognized reference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single id parameter, so baseline is 3. The description earns a point by enumerating the accepted reference prefixes (TA, NG, CG, QS, IPG, DG, HST), which tells an agent what a valid identifier looks like beyond the one example in the schema.

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 names a specific verb and resource -- 'the published record for one piece of NICE guidance by reference number' -- and gives concrete reference formats (TA1040, NG101, CG81, QS12, IPG123, DG55, HST20). That makes it clearly a single-record lookup rather than a search or list, though it never names the sibling tools it differs from.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: the tool is for looking up one known guidance by its identifier. There is no explicit guidance about when to prefer nice_search_guidance or nice_guidance_by_topic, and no statement about what happens with an unknown or malformed reference.

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.