Skip to main content
Glama
Open Drug Data MCP
by knorby

Search products across open drug data sources

drugdata_search_products
Read-onlyIdempotent

Search products by name, brand, ingredient, barcode, or NDC across openFDA, DSLD, RxNorm, and DailyMed. Returns evidence-grouped records with source conflicts, coverage status, and next steps.

Instructions

Search products across openFDA, DSLD, INKEEDecoder, RxNorm, and DailyMed. Start free text with type 'name'; use 'brand' deliberately for brand-only search, which covers fewer sources. If a full product name has no matches, retry type 'name' with only the brand (Natrol) or only the ingredient (melatonin); compare brand, variant, strength, and dosage form before selecting a record. Use ingredient, barcode, or ndc when appropriate, and pass category medication/supplement/cosmetic when known. Returns evidence-grouped entities with original records, confirmed links, source-attributed conflicts, unconfirmed candidates, and per-entity nextSteps. A product RxCUI or shared name alone does not merge products. For source+id use drugdata_get_product instead. Default searches return lightweight evidence without identity resolution; resolve_identities: true opts in to enrichment of at most five entities, concurrency three, within the shared 45-second default deadline. Read partial, coverage, and sources (status ok/error/timeout); completed results survive a timeout. One page applies to every source and re-queries all of them; each source's hasMore is independent. Selectively fetch supplied URLs only when more page content is needed. No matches is normal, not an error.

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": {
      "type": "<type>",
      "query": "<query>"
    },
    "name": "drugdata_search_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for the fan-out, starting at 1. One page applies to every source and re-queries all of them.
typeYesWhat to search by: 'name' for a product name, 'brand' for a brand name, 'ingredient' for an ingredient name, 'barcode' for a UPC/EAN, or 'ndc' for an NDC.
queryYesThe search value, as text or an identifier.
categoryNoOptional category filter: 'medication', 'supplement', or 'cosmetic'. Only sources about that category are queried.
response_formatNoText format: 'markdown' for a readable grouped report, or 'json' for the structured result serialized as JSON.markdown
resolve_identitiesNoOpt in to identity enrichment for at most five entities, concurrency three. Default false: return lightweight search evidence and resolution nextSteps.

Output Schema

NameRequiredDescriptionDefault
pageYes
typeYes
queryYes
partialYes
sourcesYes
categoryNo
coverageYes
entitiesYes
nextStepsYes
truncatedYes
entitiesOmittedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses the enrichment budget (max five entities, concurrency three, 45-second shared deadline), default lightweight vs. resolve_identities opt-in behavior, and that completed results survive a timeout. It also explains result composition (evidence groups, conflicts, unconfirmed candidates), pagination semantics (one page fans out to all sources; hasMore is per-source), and that no matches is expected rather than an error.

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?

Front-loaded with purpose, then search strategy, then result and failure semantics — a sensible order with no filler sentences. It is dense and long for a single paragraph, and the pagination sentence duplicates the schema's page property description, costing some tightness.

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

Completeness5/5

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

For a six-parameter, multi-source fan-out search with an output schema, the description covers the remaining risk areas: strategy selection, enrichment budget, partial/coverage/source status handling, and timeout behavior. Nothing an agent needs in order to call this correctly and interpret a partial result is missing.

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?

Schema coverage is 100%, so the baseline is 3; the description still adds meaning the schema lacks, notably that 'brand' covers fewer sources and that 'name' should be the default entry point with brand/ingredient retries. It does not, however, add format detail for barcode or ndc beyond the enum values already documented.

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

Purpose5/5

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

The description opens with a specific verb and resource ("Search products") plus the exact set of upstream sources queried. It explicitly demarcates the boundary with the sibling drugdata_get_product ("For source+id use drugdata_get_product instead"), so an agent can choose between them without inspecting either schema.

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

Usage Guidelines5/5

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

Guidance is prescriptive and conditional: start with type 'name', reserve 'brand' deliberately because it covers fewer sources, retry with brand-only or ingredient-only when a full name misses, and pass category when known. It also names the alternative tool for the source+id case, so both when-to-use and when-not-to-use are covered.

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