Skip to main content
Glama
mymedi-ai-mcp-server

mymedi-ai-mcp-server

by MyMedi-AI

Drug label and adverse-event lookup (OpenFDA)

drug_lookup
Read-only

Retrieve FDA drug label data, adverse-event reports, and related diagnosis codes by drug name to support clinical and billing decisions.

Instructions

Look up drug information including label data, adverse events, and related diagnosis codes. Source: openFDA (FDA drug labels and adverse-event reports); related diagnosis codes come from the MyMedi-AI code database.

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": {
      "drugName": "<drugName>"
    },
    "name": "drug_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
drugNameYesDrug name (brand, generic, or substance — min 2 chars)
searchFieldNoSearch field (default: brand_name)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.7.9
    • addedInput schema / properties / drugName / maxLength
      Added value: +500
  2. Addedv1.2.1

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so safety is covered. The description usefully adds data provenance (openFDA plus an internal code database), which tells the agent about source reliability. However, it does not explain the return shape, why idempotentHint is false, or any rate-limit/latency behavior for an external API.

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 sentences, no filler, with the data scope front-loaded and provenance placed second. It could be tightened by clarifying what the primary return value is, but there is no padding.

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?

There is no output schema, so the description carries the burden of explaining what comes back. Listing three heterogeneous data types without saying how they are structured, combined, or paginated leaves a real gap for an agent deciding whether this single call suffices.

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 description coverage is 100%, so both drugName and searchField are fully documented in the schema, including the enum values and default. The description adds nothing about parameters, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a verb and resource ('Look up drug information') and enumerates three data types (label data, adverse events, diagnosis codes), but it is ambiguous about whether all three are returned in one call or which one dominates. It also fails to distinguish the tool from siblings like drug_rxnorm, drug_interactions, and drug_enrich, which also look up drugs.

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?

No guidance is given on when to choose this tool over the many drug-related siblings (drug_rxnorm, drug_enrich, drug_interactions). There are no prerequisites, exclusions, or routing hints; the agent must infer everything from the name.

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