Skip to main content
Glama

Rxnorm Search

rxnorm_search
Read-onlyIdempotent

Look up a medication's RxCUI and MAP A BRAND DRUG TO ITS GENERIC INGREDIENT (and vice versa), e.g. Eliquis -> apixaban, Lipitor -> atorvastatin. Search by brand or generic name; returns RxCUI IDs, names, synonyms, and term types (BN=brand, IN=ingredient, SBD=dose form). The right tool for "what is the RxCUI for X", "what generic ingredient does brand X map to", or "brand vs generic name". Start here to find a drug's unique ID.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "Ozempic"
    },
    "name": "rxnorm_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesDrug name to search for, brand or generic (e.g., "Ozempic", "semaglutide", "metformin")

Output Schema

NameRequiredDescriptionDefault
nameYesNormalized drug name from search
concept_groupsYesGroups of drug concepts organized by term type

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / name / description
      Previous value: -"Drug name to search for — brand or generic (e.g., \"Ozempic\", \"semaglutide\", \"metformin\")"New value: +"Drug name to search for, brand or generic (e.g., \"Ozempic\", \"semaglutide\", \"metformin\")"
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "concept_groups": {
      +      "description": "Groups of drug concepts organized by term type",
      +      "items": {
      +        "properties": {
      +          "concepts": {
      +            "description": "Drug concepts in this group",
      +            "items": {
      +              "properties": {
      +                "language": {
      +                  "description": "Language code (typically ENG)",
      +                  "type": "string"
      +                },
      +                "name": {
      +                  "description": "Drug name",
      +                  "type": "string"
      +                },
      +                "rxcui": {
      +                  "description": "RxNorm concept unique identifier",
      +                  "type": "string"
      +                },
      +                "synonym": {
      +                  "description": "Alternative name or null",
      +                  "type": [
      +                    "string",
      +                    "null"
      +                  ]
      +                },
      +                "tty": {
      +                  "description": "Term type code",
      +                  "type": "string"
      +                }
      +              },
      +              "required": [
      +                "rxcui",
      +                "name",
      +                "tty",
      +                "language"
      +              ],
      +              "type": "object"
      +            },
      +            "type": "array"
      +          },
      +          "term_type": {
      +            "description": "RxNorm term type (BN, IN, SBD, SCD, GPCK, BPCK)",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "term_type",
      +          "concepts"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "name": {
      +      "description": "Normalized drug name from search",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "name",
      +    "concept_groups"
      +  ],
      +  "type": "object"
      +}
  3. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "name": "Ozempic"
      +  },
      +  {
      +    "name": "metformin"
      +  }
      +]
  4. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds behavior beyond that: it discloses that results include term-type codes with their meanings (BN=brand, IN=ingredient, SBD=dose form) and that the lookup works in both directions, which tells the agent how to interpret and use the output rather than just that it is a safe read.

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?

The core mapping capability and an example are front-loaded, and the term-type glossary is genuinely useful. There is mild redundancy — the example queries and the closing "Start here to find a drug's unique ID" restate the same RxCUI-lookup use case already implied by the opening, and the all-caps emphasis is unnecessary.

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

Completeness4/5

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

For a single-parameter, read-only search with annotations and an output schema, the definition covers purpose, both mapping directions, expected input forms, and how to read term types — enough to call it correctly. The only gap is not indicating where the agent should go next for NDC codes, properties, or related concepts, which the sibling set suggests would be useful.

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?

With one parameter at 100% schema description coverage, the schema already documents that `name` accepts a brand or generic drug name and even supplies examples. The description's "Search by brand or generic name" largely restates that, adding only the mapping intent rather than new syntax, matching, or formatting guidance for the parameter. Baseline 3 applies since the schema carries the parameter burden.

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?

States a specific verb (look up / map) and resource (medication, RxCUI, brand vs generic ingredient) with concrete examples (Eliquis -> apixaban). The bidirectional brand-to-generic mapping and the returned fields (RxCUI, names, synonyms, term types) make it unmistakable what this tool does versus a properties or NDC lookup.

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

Usage Guidelines4/5

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

Gives explicit trigger queries ("what is the RxCUI for X", "what generic ingredient does brand X map to", "brand vs generic name") and says "start here to find a drug's unique ID", which effectively sets it as the entry point. It does not name when to move on to siblings such as rxnorm_get_properties, rxnorm_ndc, or rxnorm_related, so the routing guidance stops short of full when-not coverage.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.