Orinyx

find_fda_label

Not for clinical use. Orinyx checks medication claims against cited FDA label text for testing and evaluation only. Do not use its results to diagnose, treat, prescribe or make patient care decisions. Use synthetic test data only. Find the FDA prescribing label Orinyx holds for a drug name or RxCUI (a brand name only where Orinyx has a curated alias for it): the SPL set ID, label version, effective date and which sections carry text. Reference text only: not a verification and not a verdict. A name that is not found is reported as given; never respell it or try a guessed alternative.

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

Input Schema

Name	Required	Description	Default
`drug`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does disclose real behavior: it returns reference text only, is explicitly not a verdict, restricts brand-name resolution to curated aliases, and specifies the not-found outcome as echoing the input verbatim rather than fuzzy-matching. It does not cover anything about caching, source recency beyond effective date, or error conditions, which keeps it below 5.

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

Conciseness3/5

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

The operative purpose sentence is buried behind three sentences of clinical-use and synthetic-data disclaimers that do not help an agent decide or invoke. The disclaimers are defensible for a medical tool, but front-loading them delays the one sentence that actually describes the action.

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 lookup with an output schema available, the description supplies what is needed: what it finds, what identifiers it accepts, alias limits, and not-found behavior. Return-value detail is correctly left to the output schema.

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 coverage is 0% and the single parameter is a bare string, so the description must compensate — and it does, stating the accepted identifiers (drug name or RxCUI) and the important caveat that brand names resolve only where a curated alias exists. It could go further by giving RxCUI format examples or stating case/whitespace handling.

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: "Find the FDA prescribing label Orinyx holds for a drug name or RxCUI," and enumerates what comes back (SPL set ID, label version, effective date, which sections carry text). That last clause implicitly separates it from read_fda_label_section, and "not a verification and not a verdict" separates it from verify_medications.

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?

Gives clear routing context: this is a reference-text lookup, not a verification, and the returned section inventory is what you would feed to read_fda_label_section. It also sets a firm constraint on lookup behavior ("A name that is not found is reported as given; never respell it or try a guessed alternative"). It stops short of naming a sibling tool explicitly for the alternative case, so not a 5.

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

All Orinyx 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.