Skip to main content
Glama

NDC format converter (10 to 11 digit)

rx_ndc_convert
Read-only

Converts a National Drug Code between FDA 10-digit layouts (4-4-2, 5-3-2, 5-4-1) and the HIPAA 11-digit 5-4-2 form, dashed or undashed. Ambiguous undashed 10-digit input is resolved against RxNav by checking all three possible layouts. Returns ndc11, ndc11_dashed, ndc10, product_ndc, segment_format, resolution method, candidate layouts, and RxNav status (ACTIVE, OBSOLETE, ALIEN, UNKNOWN) with RxCUI and concept name. Price: $0.002 per successful call, paid in USDC with x402 v2; failed calls and calls that match nothing 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": {
      "ndc": "<ndc>"
    },
    "name": "rx_ndc_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
ndcYesNDC in any common form: 0071-0155-23, 00071-0155-23, 00071015523, or 0071015523

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description goes well beyond them by disclosing the ambiguity-resolution strategy (checking all three layouts against RxNav), the returned status vocabulary with RxCUI/concept name, and an explicit pricing and charging policy including that failed or empty matches are free.

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 sentences, front-loaded with the conversion contract, then resolution behavior, then the return/pricing facts. The middle return-field enumeration is long but justified since there is no output schema; minor run-on density keeps it short of a 5.

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

Completeness5/5

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

For a single-parameter tool with no output schema, the definition supplies everything an agent needs: accepted input forms, ambiguity handling, the full result shape, status semantics, and the cost model with its billing edge cases.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With one parameter at 100% schema coverage the baseline is 3, but the description adds real meaning: it confirms dashed and undashed forms are both valid and explains what happens when an undashed 10-digit string is ambiguous, which the schema examples alone do not convey.

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 and resource ("Converts a National Drug Code") and enumerates the exact source layouts (4-4-2, 5-3-2, 5-4-1) and the target HIPAA 5-4-2 form. An agent can distinguish this normalization utility from rx_ndc or rx_drug purely from this sentence.

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?

Usage is implied well: any common NDC form is accepted, and ambiguous undashed 10-digit input gets resolved against RxNav. However, it never names an alternative tool or states a condition for choosing this converter over rx_ndc for NDC lookups, so routing is left to inference.

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