Skip to main content
Glama

Rxnorm

by io.github.pipeworx-io

Discover Tools

discover_tools
Read-onlyIdempotent

Find tools by describing the data or task. Use when you need to browse, search, look up, or discover what tools exist for: SEC filings, financials, revenue, profit, FDA drugs, adverse events, FRED economic data, Census demographics, BLS jobs/unemployment/inflation, ATTOM real estate, ClinicalTrials, USPTO patents, weather, news, crypto, stocks. Returns the top-N most relevant tools with names, descriptions, and full input schemas (with curated examples) — each result is ready to call directly, no second schema lookup needed. Call this FIRST when you have many tools available and want to see the option set (not just one answer).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoAlias for query.
taskNoAlias for query.
limitNoMaximum number of tools to return (default 20, max 50)
queryYesNatural language description of what you want to do (e.g., "analyze housing market trends", "look up FDA drug approvals", "find trade data between countries"). Accepts task, q, description, search as aliases.
searchNoAlias for query.
descriptionNoAlias for query.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed5 schema fields changed
    • addedInput schema / properties / description
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
    • addedInput schema / properties / q
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
    • changedInput schema / properties / query / description
      Previous value: -"Natural language description of what you want to do (e.g., \"analyze housing market trends\", \"look up FDA drug approvals\", \"find trade data between countries\")"New value: +"Natural language description of what you want to do (e.g., \"analyze housing market trends\", \"look up FDA drug approvals\", \"find trade data between countries\"). Accepts task, q, description, search as aliases."
    • addedInput schema / properties / search
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
    • addedInput schema / properties / task
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "look up FDA drug approvals"
+  },
+  {
+    "query": "analyze housing market trends"
+  }
+]
  3. 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=true, destructiveHint=false, idempotentHint=true. The description adds behavioral context: returns top-N results with full schemas and examples, ready to call directly. No contradiction with annotations.

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 two sentences, front-loading the purpose. The second sentence is long with many examples but remains informative. Could be slightly more concise, but is generally well-structured.

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?

The description explains the output structure (top-N tools with names, descriptions, full schemas) and the intended use case (call first). With good annotations and no output schema needed, it covers essential information for a discovery tool.

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% with clear parameter descriptions and aliases. The description mentions the 'query' parameter as natural language, but does not add significant meaning beyond the schema. Baseline 3 is appropriate given high coverage.

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 specific verbs like 'browse, search, look up, discover' and lists numerous example domains. It clearly states the tool's function as finding tools by describing a data or task, and distinguishes it from siblings by recommending it as a first call to see the option set.

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 when to use ('when you need to browse, search, look up, or discover what tools exist for...') and advises calling it first. It implies it is for discovery rather than direct answer retrieval, but lacks explicit when-not-to-use guidance.

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

All Rxnorm toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation2/5

Several tools blur together: ask_pipeworx_beta currently duplicates ask_pipeworx exactly, ask_pipeworx/ask_pipeworx_grounded/deep_research/validate_claim all route natural-language questions to data sources, and the prediction-market tools (polymarket_edges, polymarket_arbitrage, polymarket_fill_risk, bet_research) have fuzzy boundaries. The detailed descriptions help, but an agent can easily misselect among them.

Naming Consistency3/5

All names are lowercase snake_case and the rxnorm_, polymarket_, and pipeworx_ prefixes create readable groupings, but the set mixes imperative verb-object names (validate_claim, list_subscriptions), noun-phrase names (entity_profile, recent_alerts), and bare verbs (remember, forget). It is readable but not a predictable uniform naming convention.

Tool Count2/5

35 tools is in the too-many band for a coherent server, and the Rxnorm identity makes it worse: only 4 tools are actually RxNorm-specific while 31 are unrelated Pipeworx, prediction-market, memory, and utility tools. A focused RxNorm server would need a fraction of this surface.

Completeness3/5

The four rxnorm_* tools plus resolve_entity cover the main RxNorm lookup flow (search, properties, related, NDC), so the core is not broken. But the set lacks a reverse NDC-to-concept lookup and the 31 non-RxNorm tools do not complete any single coherent domain, leaving notable gaps relative to the server's stated purpose.

Resources