Skip to main content
Glama
Drug Labeling MCP Server

Drug Labeling MCP Server

Get Drug Cyp Label Details

get_drug_cyp_label_details

Retrieve CYP metabolism and interaction evidence for specified targets from a single FDA drug labeling record to support interaction and safety assessments.

Instructions

Retrieve CYP evidence for one FDA labeling record.

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": {
      "record_id": "<record_id>",
      "cyp_targets": "<cyp_targets>"
    },
    "name": "get_drug_cyp_label_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
record_idYes
cyp_targetsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden, yet it discloses nothing beyond the bare purpose. It does not confirm this is a read-only lookup, explain how cyp_targets scopes results, or note any confirmation, limits, or empty-result behavior for an unknown record_id.

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. Its brevity is efficient structurally, though the terseness pushes all necessary detail onto undocumented schema fields.

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

Completeness2/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 not be described. However, for a two-required-parameter tool with zero annotation and zero schema-description coverage, the description leaves the critical cyp_targets semantics and any usage context entirely unaddressed.

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 required parameters. The phrase 'one FDA labeling record' weakly implies record_id identifies the record, but cyp_targets is left entirely unexplained — no hint that it is a list of CYP enzyme names, no accepted naming convention, no note on whether results are unioned or filtered.

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 (Retrieve) and resource (CYP evidence for one FDA labeling record), which is clearly distinguishable from the mutation-free siblings. It does not explicitly contrast itself with get_drug_cyp_label_history, and 'CYP evidence' remains somewhat jargon-heavy, but the core purpose is legible.

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?

The description offers no when-to-use guidance, no prerequisites, and never names an alternative such as get_drug_cyp_label_history for historical lookups. The agent must infer selection purely from the tool name.

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