Skip to main content
Glama

Nice Search Guidance

nice_search_guidance
Read-onlyIdempotent

Search NICE guidance for England by drug, device, procedure or condition, technology appraisals, NICE and clinical guidelines, diagnostics guidance, interventional procedures and quality standards. Returns the reference number (TA1040, NG101), title, guidance type, publication date and summary. Answers whether NICE has assessed a treatment and which document says so, which is the first step to whether the NHS in England funds 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": {
      "limit": 3,
      "query": "olaparib"
    },
    "name": "nice_search_guidance"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoResult page, 1-based
sortNo"date" for newest first, or "relevance" (default)
limitNoResults to return, 1-50 (default 15)
queryYesDrug, device, procedure or condition, e.g. "olaparib" or "atrial fibrillation"
guidance_typeNoRestrict to one NICE programme, spelled as NICE spells it: Antimicrobial prescribing guidelines, Antimicrobial resistance guidance, Cancer service guidelines, Clinical guidelines, COVID-19 rapid guidelines, Diagnostics guidance, Early value assessment, Health technology evaluations, HealthTech guidance, Highly specialised technologies guidance, Interventional procedures guidance, Late stage assessment, Medical technologies guidance, NICE guidelines, Public health guidelines, Safe staffing guidelines, Social care guidelines, Technology appraisal guidance

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is covered. The description adds genuinely new information beyond them: it names the exact fields returned (reference number such as TA1040/NG101, title, guidance type, publication date, summary), which matters because there is no output schema. It does not mention pagination limits or result-shape caveats, keeping it short of 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 scope and coverage, then the return fields and the motivating question. The enumeration of guidance families is a bit long, but each clause is doing identifiable work; there is no filler.

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 five parameters, no output schema and annotations covering safety, the description does what matters: geographic scope (England), the kinds of guidance, and the return fields. Pagination and sorting behavior are left to the schema, which documents them, so nothing essential for a correct call is missing.

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 every parameter including page, sort, limit, query and the full guidance_type enumeration documented inline. The description echoes the guidance families but adds no syntax, defaults or filtering semantics beyond the schema, so the baseline of 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?

The description opens with a specific verb and resource: 'Search NICE guidance for England by drug, device, procedure or condition', and enumerates the guidance families covered (technology appraisals, diagnostics guidance, interventional procedures, quality standards). It is clear what the tool does, but it never distinguishes itself from siblings such as nice_guidance, nice_guidance_by_topic or nice_recent_guidance, so an agent cannot tell from this text alone which NICE search to pick.

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 supplies a concrete use case: answering 'whether NICE has assessed a treatment and which document says so', framed as the first step toward NHS England funding. That gives a clear context for reaching for this tool. It stops short of exclusions or naming alternatives, so the agent must still infer when a different NICE tool is the better choice.

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.