Skip to main content
Glama

Rxnorm Get Properties

rxnorm_get_properties
Read-onlyIdempotent

Get full medication details by RxCUI ID. Returns name, synonyms, term type, language, and status. Use after rxnorm_search to retrieve complete drug information.

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_get_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
rxcuiYesRxNorm concept ID (e.g., "7052" for metformin) OR a drug name (e.g. "aspirin", "Tylenol"), names are resolved to an RxCUI automatically.

Output Schema

NameRequiredDescriptionDefault
ttyYesTerm type code
nameYesDrug name
rxcuiYesRxNorm concept unique identifier
synonymNoAlternative name or null
languageYesLanguage code
suppressYesSuppression status flag

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / rxcui / description
      Previous value: -"RxNorm concept ID (e.g., \"7052\" for metformin) OR a drug name (e.g. \"aspirin\", \"Tylenol\") — names are resolved to an RxCUI automatically."New value: +"RxNorm concept ID (e.g., \"7052\" for metformin) OR a drug name (e.g. \"aspirin\", \"Tylenol\"), names are resolved to an RxCUI automatically."
  2. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
      -  {
      -    "rxcui": "7052"
      -  },
      -  {
      -    "rxcui": "1243465"
      -  }
      -]New value: +[
      +  {
      +    "rxcui": "7052"
      +  },
      +  {
      +    "rxcui": "83367"
      +  }
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / rxcui / description
      Previous value: -"RxNorm concept ID (e.g., \"7052\" for metformin)"New value: +"RxNorm concept ID (e.g., \"7052\" for metformin) OR a drug name (e.g. \"aspirin\", \"Tylenol\") — names are resolved to an RxCUI automatically."
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "language": {
      +      "description": "Language code",
      +      "type": "string"
      +    },
      +    "name": {
      +      "description": "Drug name",
      +      "type": "string"
      +    },
      +    "rxcui": {
      +      "description": "RxNorm concept unique identifier",
      +      "type": "string"
      +    },
      +    "suppress": {
      +      "description": "Suppression status flag",
      +      "type": "string"
      +    },
      +    "synonym": {
      +      "description": "Alternative name or null",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "tty": {
      +      "description": "Term type code",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "rxcui",
      +    "name",
      +    "tty",
      +    "language",
      +    "suppress"
      +  ],
      +  "type": "object"
      +}
  5. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "rxcui": "7052"
      +  },
      +  {
      +    "rxcui": "1243465"
      +  }
      +]
  6. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive behavior, so the safety profile is covered. The description adds only a field listing (name, synonyms, term type, language, status), which is largely redundant with the existing output schema; no rate limits, error behavior, or resolution caveats are mentioned.

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?

Three short sentences, front-loaded with the action and followed by the return payload and the sequencing hint. The phrase 'complete drug information' mildly restates 'full medication details' but no sentence is wasteful.

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 one parameter, full schema coverage, an output schema and rich annotations, the description covers what is needed to invoke the tool correctly. The only gap is the failure to reflect that free-text drug names are accepted inputs.

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% and the schema already documents that a drug name is auto-resolved to an RxCUI. The description's phrase 'by RxCUI ID' actually narrows the accepted input versus the schema, adding no positive semantics and mildly understating capability; baseline 3 applies.

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 and resource (get full medication details) keyed by RxCUI ID, and names the return payload. It is distinguishable from rxnorm_search via the sequencing note, though it does not differentiate from siblings like rxnorm_ndc or rxnorm_related.

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?

Explicitly says to use it after rxnorm_search to retrieve complete drug information, giving a clear position in a lookup workflow. It stops short of when-not-to-use guidance or naming alternatives such as rxnorm_related for associated concepts.

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.