Skip to main content
Glama

NIH RxNorm concept lookup: RxCUI identifiers for a drug

health_rxnorm_concept_id
Read-only

NIH RxNorm concept lookup (RxNav): RxCUI identifiers for a drug name with each concept's name and term type (e.g. IN = ingredient, SCD = clinical drug). Up to 5 concepts per call. Exact-name lookup, no fuzzy matching. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "name": "<name>"
    },
    "name": "health_rxnorm_concept_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNoHow many concepts, 1 to 5 (default 3)
nameYesDrug or ingredient name, letters, digits, spaces and hyphens, 2 to 100 characters

Output Schema

NameRequiredDescriptionDefault
queryNo
totalNo
sourceNo
conceptsNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnlyHint and openWorldHint, so the description's value-add is cost and failure behavior: $0.002 per successful call via x402 across multiple networks and no charge on failure — material for an agent deciding whether to call. The 5-concept cap and no-fuzzy constraint are also disclosed. It stops short of covering latency or rate limits.

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?

One front-loaded paragraph: purpose first, then result format, then limits, then pricing. Dense but each clause carries information. The enumerated list of payment networks ('Solana and 10 more networks') is the only mildly expendable detail.

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?

An output schema exists, so return values needn't be explained, and the description covers the remaining decision-relevant facts: scope of matching, result cap, and cost model. Only rate limits and error semantics beyond 'not charged' are unaddressed, which is minor for a read-only lookup.

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%, so both parameters are already documented with types, ranges, defaults, and the allowed character set. The description only restates the 5-concept maximum and adds the term-type vocabulary, which is useful context but not new parameter-level meaning.

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+resource (RxNorm concept lookup returning RxCUI identifiers for a drug name) and explains what each result contains (concept name plus term type with examples IN/SCD). This clearly separates it from siblings like health_drugbank_interaction or health_daily_med_label_spl.

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?

'Exact-name lookup, no fuzzy matching' plus the 5-concept cap tells the agent the conditions under which this tool will and will not succeed. It does not name a sibling alternative for fuzzy/substring matching, so no explicit routing, but the constraint is clear enough to gate usage.

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.

Resources