Skip to main content
Glama

Rxnorm

by io.github.pipeworx-io

Remember

remember
Idempotent

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference")
valueYesValue to store (any text — findings, addresses, preferences, notes)

Schema Changelog

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

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Adds context beyond annotations: persistence duration (24h anonymous), scope by identifier, and intended use as storage. No contradictions with annotations (idempotentHint true, destructiveHint false).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, front-loaded with purpose, each sentence adds unique value. No redundant or filler content.

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?

No output schema, but description fully covers purpose, usage, behavioral details, and parameter guidance. Complete for a storage tool with simple key-value semantics.

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?

Schema already has 100% coverage with descriptions. Description adds value by providing example keys and values (e.g., 'subject_property', 'target_ticker'), enhancing semantics beyond schema alone.

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?

Description uses specific verb 'Save data' and resource 'key-value pair' with concrete examples (resolved ticker, target address). Clearly distinguishes from siblings recall and forget.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use ('when you discover something worth carrying forward') and pairs with recall and forget. Mentions scoping and persistence differences between authenticated and anonymous sessions.

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