Skip to main content
Glama
Drug Labeling MCP Server

Drug Labeling MCP Server

Historical CYP Drug Label Timeline

get_drug_cyp_label_history
Read-onlyIdempotent

Retrieves available FDA drug-label revisions and passages mentioning specified CYP enzymes, helping users trace metabolism and interaction evidence over time.

Instructions

Retrieve available label revisions and passages mentioning target CYP enzymes.

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": {
      "drug_name": "<drug_name>",
      "cyp_targets": "<cyp_targets>"
    },
    "name": "get_drug_cyp_label_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
drug_nameYes
cyp_targetsYes

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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds only the mild signal that results are limited to "available" revisions and are filtered to passages matching the CYP targets. It says nothing about ordering, time coverage, pagination, or what constitutes a "revision," which matters for a history-oriented, open-world 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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though the thinness means brevity comes at the cost of substance rather than through tight editing of richer content.

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?

The presence of an output schema removes the need to describe return values, and the tool has only two parameters, keeping complexity low. Still, with zero schema coverage on inputs and no differentiation from get_drug_cyp_label_details, the definition leaves meaningful gaps for an agent deciding whether and how to call it.

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% for both parameters, so the description must compensate and does not. It hints that cyp_targets are enzyme names, but gives no naming convention (e.g., CYP3A4 vs 3A4), no matching semantics (exact vs substring), and no drug_name format expectations. An agent would be guessing about valid input values.

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 states a specific verb ("Retrieve") and a concrete resource: label revisions plus passages mentioning target CYP enzymes. An agent can tell this is a historical/timeline lookup rather than a current-label lookup. However, it never distinguishes itself from the sibling get_drug_cyp_label_details, which likely returns the same label content without the history dimension.

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, no prerequisite context, and no mention of when to prefer the details or generic label siblings instead. The word "available" vaguely implies that not all revisions may exist, but this is inference, not stated guidance.

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