Skip to main content
Glama
Drug Labeling MCP Server

Drug Labeling MCP Server

Get Latest Four Opioid Labels

get_latest_four_opioid_labels
Read-only

Retrieve openFDA records for four configured opioids and generate an LLM summary, helping users compare drug-labeling information in one response.

Instructions

Latest available openFDA record for four configured opioids, with LLM summary.

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": "get_latest_four_opioid_labels"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds one genuinely useful behavioral fact beyond that — the result includes an LLM-generated summary — but says nothing about which four opioids are fixed, freshness/recency semantics, or any caching or rate-limit behavior.

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?

A single front-loaded clause with no filler. It is a sentence fragment rather than a complete sentence, and 'four configured opioids' is left unexplained, which slightly undercuts otherwise excellent economy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, but the core scoping fact — which four opioids are configured and whether that set is fixed — is never stated, leaving an agent unable to judge whether this tool answers a question about a specific drug.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The mention of 'four configured opioids' hints that selection is hardcoded rather than caller-specified, which is consistent with the empty 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 resource (latest openFDA opioid label record) and adds scope ('four configured opioids') plus a distinguishing feature ('with LLM summary'). It is clear enough to separate from search_opioid_label_updates or get_drug_label, but it never explicitly contrasts itself with them.

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

Usage Guidelines2/5

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

There is no when-to-use guidance: nothing says to pick this for a quick snapshot versus search_opioid_label_updates for filtered searching or get_drug_label for a single drug. Usage is only inferable from the word 'latest'.

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