Rxnorm

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.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`rxcui`	Yes	RxNorm concept ID (e.g., "7052" for metformin) OR a drug name (e.g. "aspirin", "Tylenol") — names are resolved to an RxCUI automatically.

Output Schema

TableJSON Schema

Name	Required	Description
`tty`	Yes	Term type code
`name`	Yes	Drug name
`rxcui`	Yes	RxNorm concept unique identifier
`synonym`	No	Alternative name or null
`language`	Yes	Language code
`suppress`	Yes	Suppression status flag

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 3, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "rxcui": "7052"
-  },
-  {
-    "rxcui": "1243465"
-  }
-]New value: +[
+  {
+    "rxcui": "7052"
+  },
+  {
+    "rxcui": "83367"
+  }
+]

Changed1 schema field changedJul 13, 2026

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."

Changed1 schema field changedMay 8, 2026

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

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "rxcui": "7052"
+  },
+  {
+    "rxcui": "1243465"
+  }
+]

First observedApr 22, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already cover safety characteristics (readOnlyHint, idempotentHint, non-destructive), so the description does not need to repeat them. The description adds workflow and return-field context, but does not disclose any distinctive behavioral traits beyond what annotations and the schema provide.

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 three short sentences with the action, return fields, and workflow context front-loaded. The only minor issue is redundancy between 'full medication details' and 'complete drug information,' which prevents a perfect score.

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 tool with an output schema and strong annotations, the description is nearly complete: it names the expected input type, highlights return fields, and links to the correct preceding tool. The main gap is lack of explicit sibling exclusions, but this is not critical given the simple scope.

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 coverage is 100%, and the parameter description already explains that rxcui accepts either an RxCUI ID or a drug name that is resolved automatically. The tool description only repeats 'by RxCUI ID' and actually understates the name-resolution behavior, so it adds no extra semantic value here.

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 uses a specific verb and resource ('Get full medication details by RxCUI ID') and lists concrete return fields: name, synonyms, term type, language, and status. It also names rxnorm_search as the preceding workflow step, which helps distinguish this property-lookup tool from the search sibling.

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?

The description explicitly says 'Use after rxnorm_search to retrieve complete drug information,' which gives clear workflow context for when this tool should be called. It does not explicitly say when not to use rxnorm_related or rxnorm_ndc, so it stops short of full when-not/alternative guidance.

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

All Rxnorm tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.