Skip to main content
Glama

Nice Guidance By Topic

nice_guidance_by_topic
Read-onlyIdempotent

Every piece of NICE guidance filed under a condition area, e.g. all breast cancer guidance, or all guidance on type 2 diabetes, with reference numbers, titles, programme and dates. This is the complete curated list for the topic rather than a relevance-ranked search, so it is the right tool for "what has NICE published on X". Call with no topic to list the condition areas that can be asked for.

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": 4,
      "topic": "breast cancer"
    },
    "name": "nice_guidance_by_topic"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoItems to return, 1-200 (default 60)
topicNoCondition area, e.g. "breast cancer", "diabetes"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds value beyond that by describing the completeness guarantee of the result set and the fields returned, and by noting the no-topic behavior that returns the list of condition areas.

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?

Front-loaded with the core statement of scope, followed by the differentiator and then the empty-argument behavior. The first sentence is dense but every clause carries useful information; no filler is present.

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?

For a two-parameter read tool with no output schema, the definition covers scope, result fields, alternative-approach guidance and zero-argument behavior. Nothing an agent needs in order to call it correctly is missing.

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%, so the baseline is 3, but the description adds real meaning by explaining that omitting `topic` returns the list of available condition areas rather than empty results. The `limit` parameter is left to the schema, which documents its range and default adequately.

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?

Names a specific resource (NICE guidance filed under a condition area) and its scope (the complete curated list, not a ranked search), and enumerates returned fields (reference numbers, titles, programme, dates). An agent can distinguish it from the search-style siblings without opening the 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?

Gives an explicit use case ("what has NICE published on X") and contrasts it with relevance-ranked search, which implicitly rules out the search sibling. It does not name that sibling tool outright, so the agent must infer which one to avoid.

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.