Orinyx

read_fda_label_section

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. Read one section of a cached FDA prescribing label by its SPL set ID. section is one of: contraindications, boxed_warning, warnings, warnings_and_cautions, overdosage, dosage_and_administration, indications_and_usage, drug_interactions, dosage_forms_and_strengths. A long section comes in parts; when the reply says TRUNCATED, call again with the offset it gives before relying on the text. version reads a superseded label version and the reply says so. When one set ID backs two drugs the reply asks for rxcui: pass the one find_fda_label showed. Reference text, not a verdict and not clinical advice.

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": {
      "set_id": "<set_id>",
      "section": "<section>"
    },
    "name": "read_fda_label_section"
  }
}

Input Schema

Name	Required	Description	Default
`rxcui`	No
`offset`	No
`set_id`	Yes
`section`	Yes
`version`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4.7/5.0

Behavior5/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 so: it discloses that labels are cached, that long sections return in parts with a TRUNCATED marker, that a version request is echoed as superseded, that ambiguous set IDs trigger a prompt for rxcui, and that the output is reference text rather than a verdict. It also states the non-clinical-use boundary and the synthetic-test-data rule, which an agent cannot get from any structured field.

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 operational content is front-loaded and well ordered: scope disclaimer, then what the tool does, then each parameter's recovery path. The main inefficiency is the disclaimer appearing at both the opening and the closing line ("Reference text, not a verdict and not clinical advice"), which repeats the non-clinical-use framing three times.

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 five-parameter read tool with an output schema, nothing essential is missing: prerequisite discovery tool, pagination recovery, version selection, disambiguation path, and permissible-use boundary are all covered. Return-value shape is properly left to the output schema.

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

Parameters5/5

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

Schema coverage is 0%, so the description must compensate, and it does: it supplies the authoritative enumeration of valid `section` values, which the schema leaves as an unconstrained string, and it explains the trigger conditions for `offset`, `version`, and `rxcui`. It also clarifies that `set_id` comes from find_fda_label and that `rxcui` should be the value that tool surfaced.

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 ("Read one section of a cached FDA prescribing label") and pins the retrieval key ("by its SPL set ID"). It also implicitly separates itself from find_fda_label, which is named as the source of the set ID, and from read_otc_monograph_section by scoping to FDA prescribing labels.

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 concrete conditional guidance for the optional parameters: use `version` when a superseded label is needed, use `offset` when the reply says TRUNCATED, and pass `rxcui` when a set ID maps to two drugs. It lacks an explicit statement of when to reach for this tool versus read_otc_monograph_section or find_fda_label, leaving that routing to be inferred.

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.