Skip to main content
Glama

Rxnorm Related

rxnorm_related
Read-onlyIdempotent

Find related medications by RxCUI, brands, generics, ingredients, and dose forms. Maps between brand and generic alternatives. Use to compare drug options.

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": {
      "rxcui": "7052"
    },
    "name": "rxnorm_related"
  }
}

Input Schema

NameRequiredDescriptionDefault
ttyNoOptional term type filter: BN (brand name), IN (ingredient), SBD (semantic branded drug), SCD (semantic clinical drug), GPCK (generic pack), BPCK (branded pack); other RxNorm term types such as PIN, MIN, DF and DFG also work. For several, separate them with a comma, a plus or a space, "BN,SBD", "BN+SBD" and "BN SBD" are all accepted and equivalent. Case does not matter. Omit for the default set (IN, BN, SBD, SCD, GPCK, BPCK).
rxcuiYesRxNorm concept ID, or a drug name (e.g. "aspirin"), resolved to an RxCUI automatically.

Output Schema

NameRequiredDescriptionDefault
rxcuiYesRxNorm concept unique identifier
related_groupsYesGroups of related drug concepts by term type

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / rxcui / description
      Previous value: -"RxNorm concept ID, or a drug name (e.g. \"aspirin\") — resolved to an RxCUI automatically."New value: +"RxNorm concept ID, or a drug name (e.g. \"aspirin\"), resolved to an RxCUI automatically."
    • changedInput schema / properties / tty / description
      Previous value: -"Optional term type filter: BN (brand name), IN (ingredient), SBD (semantic branded drug), SCD (semantic clinical drug), GPCK (generic pack), BPCK (branded pack); other RxNorm term types such as PIN, MIN, DF and DFG also work. For several, separate them with a comma, a plus or a space — \"BN,SBD\", \"BN+SBD\" and \"BN SBD\" are all accepted and equivalent. Case does not matter. Omit for the default set (IN, BN, SBD, SCD, GPCK, BPCK)."New value: +"Optional term type filter: BN (brand name), IN (ingredient), SBD (semantic branded drug), SCD (semantic clinical drug), GPCK (generic pack), BPCK (branded pack); other RxNorm term types such as PIN, MIN, DF and DFG also work. For several, separate them with a comma, a plus or a space, \"BN,SBD\", \"BN+SBD\" and \"BN SBD\" are all accepted and equivalent. Case does not matter. Omit for the default set (IN, BN, SBD, SCD, GPCK, BPCK)."
  2. Changed2 schema fields changed
    • changedInput schema / examples
      Previous value: -[
      -  {
      -    "rxcui": "7052"
      -  },
      -  {
      -    "rxcui": "1243465",
      -    "tty": "BN,SBD"
      -  }
      -]New value: +[
      +  {
      +    "rxcui": "7052"
      +  },
      +  {
      +    "rxcui": "83367",
      +    "tty": "BN,SBD"
      +  },
      +  {
      +    "rxcui": "83367",
      +    "tty": "BN+SBD"
      +  }
      +]
    • changedInput schema / properties / tty / description
      Previous value: -"Optional term type filter: BN (brand name), IN (ingredient), SBD (semantic branded drug), SCD (semantic clinical drug), GPCK (generic pack), BPCK (branded pack). Comma-separated for multiple."New value: +"Optional term type filter: BN (brand name), IN (ingredient), SBD (semantic branded drug), SCD (semantic clinical drug), GPCK (generic pack), BPCK (branded pack); other RxNorm term types such as PIN, MIN, DF and DFG also work. For several, separate them with a comma, a plus or a space — \"BN,SBD\", \"BN+SBD\" and \"BN SBD\" are all accepted and equivalent. Case does not matter. Omit for the default set (IN, BN, SBD, SCD, GPCK, BPCK)."
  3. Changed1 schema field changed
    • changedInput schema / properties / rxcui / description
      Previous value: -"RxNorm concept ID"New value: +"RxNorm concept ID, or a drug name (e.g. \"aspirin\") — resolved to an RxCUI automatically."
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "related_groups": {
      +      "description": "Groups of related drug concepts by term type",
      +      "items": {
      +        "properties": {
      +          "concepts": {
      +            "description": "Related drug concepts",
      +            "items": {
      +              "properties": {
      +                "name": {
      +                  "description": "Drug name",
      +                  "type": "string"
      +                },
      +                "rxcui": {
      +                  "description": "RxNorm concept unique identifier",
      +                  "type": "string"
      +                },
      +                "tty": {
      +                  "description": "Term type code",
      +                  "type": "string"
      +                }
      +              },
      +              "required": [
      +                "rxcui",
      +                "name",
      +                "tty"
      +              ],
      +              "type": "object"
      +            },
      +            "type": "array"
      +          },
      +          "term_type": {
      +            "description": "RxNorm term type filter applied",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "term_type",
      +          "concepts"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "rxcui": {
      +      "description": "RxNorm concept unique identifier",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "rxcui",
      +    "related_groups"
      +  ],
      +  "type": "object"
      +}
  5. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "rxcui": "7052"
      +  },
      +  {
      +    "rxcui": "1243465",
      +    "tty": "BN,SBD"
      +  }
      +]
  6. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this as read-only, idempotent, open-world, and non-destructive, so the safety profile is covered. The description adds useful semantic scope about brand/generic mapping and ingredient/dose-form relationships, but does not describe result shape, coverage limits, or whether relationships are directional.

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 description is short, front-loaded, and free of filler. The middle sentence about brand/generic mapping partially repeats the first sentence, which prevents a full 5.

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?

With rich schema coverage, existing annotations, and an output schema, the definition supplies enough for an agent to call the tool correctly. A small gap remains around relationship direction and scope, but nothing essential is missing.

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 parameters are already well documented, including the tty syntax and automatic drug-name resolution. The description adds no parameter-level detail beyond what the schema states, making the baseline 3 appropriate.

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 uses a specific verb and resource ('Find related medications by RxCUI...') and lists the relationship dimensions it covers, so the tool's purpose is clear. It does not explicitly differentiate itself from siblings such as rxnorm_get_properties or rxnorm_search, which keeps it from a 5.

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

Usage Guidelines3/5

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

'Use to compare drug options' implies a use case, but there is no explicit when-to-use versus when-not-to-use guidance and no named alternative tool. The direction of usage is inferable but not spelled out.

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.