UK Data for Agents

drug_pharmacologic_class

Read-onlyIdempotent

What type of drug is this? Returns a drug's Established Pharmacologic Class as used in US FDA labelling (e.g. sertraline: Serotonin Reuptake Inhibitor; simvastatin: HMG-CoA Reductase Inhibitor), via the U.S. National Library of Medicine RxClass. Useful for patients, students and agents answering 'is it an SSRI / statin / opioid?'. Classes come from FDA product labels only, so older or non-US drugs may have none; it does not describe effects, safety or dosing. (cost: 1 credit)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "drug_pharmacologic_class"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No	string, required, a generic or brand drug name (e.g. "sertraline")

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations cover read-only and idempotency, and the description adds real context beyond them: the data originates from FDA product labels only, coverage gaps are possible, and each call costs 1 credit. It does not say how many classes may be returned or how multi-class drugs are presented.

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 question it answers, then examples, source, caveats and cost in a logical order. The 'useful for patients, students and agents' clause is mild filler and the paragraph is dense, but nothing is redundant enough to hurt.

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 simple parameter, no output schema and permissive annotations, the description supplies what is missing: return content, data provenance, coverage limits and cost. The only gap is the exact response shape when a drug has several established classes.

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% and the schema already documents the single 'name' parameter including the generic-or-brand allowance. The description's examples restate the same input format rather than adding syntax or matching behavior (e.g. fuzzy matching, which sibling drug_name_match handles).

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 (Established Pharmacologic Class from FDA labelling) and gives two concrete examples (sertraline → Serotonin Reuptake Inhibitor; simvastatin → HMG-CoA Reductase Inhibitor) plus the upstream source (NLM RxClass). This clearly separates it from siblings like drug_brand_names, drug_generic_ingredient and drug_listed_uses.

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?

Frames the use case explicitly ('is it an SSRI / statin / opioid?') and states when the tool won't help ('older or non-US drugs may have none', 'does not describe effects, safety or dosing'). It does not name the specific sibling tools an agent should use for those other questions, which keeps it below a 5.

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

All UK Data for Agents tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?