Skip to main content
Glama

Nice Recommendations

nice_recommendations
Read-onlyIdempotent

The recommendations chapter of a piece of NICE guidance, in full text, the numbered paragraphs stating what NICE recommends and under what conditions, including whether a medicine is recommended only within its marketing authorisation or only under a commercial arrangement. Answers "did NICE recommend this treatment, and for whom", with the wording that decides NHS funding in England.

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_recommendations"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, open-world behavior, so the description is free to add content-level context — and it does: full text, numbered paragraphs, conditions of recommendation, and marketing-authorisation vs. commercial-arrangement caveats. It adds real domain meaning beyond the safety profile, though it says nothing about behavior for an invalid or non-existent reference number.

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 what is returned and followed by the question it answers, so an agent can decide quickly. There is mild redundancy between 'in full text' and 'the numbered paragraphs stating what NICE recommends', and the commercial-arrangement clause is dense, but nothing is wasted outright.

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 no output schema, the description must describe the return value, and it does so concretely — chapter text, numbered paragraphs, conditions, and funding-relevant caveats. For a single-parameter read tool with full annotation coverage, that is close to complete; only error/edge behavior for a bad reference number is left unaddressed.

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 coverage is 100% with a single 'id' parameter that already carries a description and an example ('TA1040'), so the schema does the heavy lifting. The description adds no additional semantics about the identifier format or what happens if a non-TA reference is supplied; baseline 3 applies.

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?

Names a specific resource — the recommendations chapter of a piece of NICE guidance — and specifies it is returned in full text, which implicitly separates it from a full-guidance sibling such as nice_guidance. It stops short of explicitly naming or contrasting the sibling tools, so the differentiation has to be inferred from 'chapter' vs. whole guidance.

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?

The framing question 'did NICE recommend this treatment, and for whom' gives a clear use case for invoking it. However, there is no explicit when-not guidance, no mention of when to prefer nice_guidance or nice_search_guidance instead, and no note on prerequisites such as needing a valid NICE reference number first.

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.