Skip to main content
Glama
Drug Labeling MCP Server

Drug Labeling MCP Server

Search Opioid Label Updates

search_opioid_label_updates

Search FDA opioid label update PDFs to retrieve relevant passages, similarity scores, and page references for evidence-grounded drug-labeling answers.

Instructions

Search FDA opioid label updates PDF.

Returns relevant passages, similarity scores, and FDA PDF page references.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_opioid_label_updates"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
top_kNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations present, the description carries the full burden and does disclose the return shape: relevant passages, similarity scores, and FDA PDF page references. It says nothing about whether retrieval is semantic or keyword-based, how ranking works, or any rate/permission constraints, which leaves real behavioral gaps for a search tool.

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 short sentences, front-loaded with the action and resource, with the return contract following. The awkward line breaks and terseness cost a little, but there is no filler.

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 needn't be re-explained and the tool is simple at two parameters. However, with zero annotation coverage and zero schema coverage, the description should have covered query formulation and top_k behavior to be genuinely complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must explain both parameters and does not. It never clarifies that 'query' is a natural-language question or that 'top_k' controls the number of returned passages (default 5), leaving the most consequential knob undocumented.

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?

States a specific verb ('Search') and a specific resource ('FDA opioid label updates PDF'), which is clearly distinct from the sibling lookup tools like get_drug_label and get_drug_cyp_label_history. It stops short of naming an alternative, but the retrieval-vs-lookup distinction is legible from the wording.

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 explicit when-to-use or when-not-to-use guidance, and no mention of the sibling tools that return whole labels instead of passages. An agent must infer that this is the tool for free-text questions rather than structured drug lookups.

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