Skip to main content
Glama

Regenstrief LOINC laboratory and clinical test codes: LOINC

health_loinc_laboratory_codes
Read-only

Regenstrief LOINC laboratory and clinical test codes (via NLM Clinical Tables): LOINC number and long common name matching a term, with total match count. Codes and names only, no units or reference ranges. Up to 20 per call. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls 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": {
      "term": "<term>"
    },
    "name": "health_loinc_laboratory_codes"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNoHow many codes, 1 to 20 (default 10)
termYesWords to search in LOINC names, 2 to 60 characters

Output Schema

NameRequiredDescriptionDefault
termNo
codesNo
totalNo
sourceNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the supplied readOnlyHint and openWorldHint, the description discloses billing behavior that materially affects invocation: $0.002 per successful call via x402 with no charge on failure, plus the hard 20-result cap. It does not cover pagination or truncation behavior when the match count exceeds 20, which is the main remaining gap.

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?

Front-loaded with the resource and source, then output shape, then scope limits, then cost. Every sentence carries information, though the payment-network enumeration ('USDC on Base, Solana and 10 more networks') is longer than an agent needs to decide or call.

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 two-parameter read-only lookup with a full schema, complete parameter docs, and an output schema, this covers purpose, output fields, cost, and result limits. The only shortfall is absent guidance on alternatives and on what happens when the total match count exceeds the 20 returned.

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 coverage is 100%, with both parameters fully documented (term length range, max range and default), so the schema already does the explanatory work. The description restates the 20-result ceiling and the term-matching behavior but adds no new syntax or format detail beyond that baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: matches a search term against LOINC numbers and long common names via NLM Clinical Tables, returning codes and names with a total match count. The data source and returned fields distinguish it clearly from other health lookup siblings, though no sibling is named explicitly.

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 by the scope note ('Codes and names only, no units or reference ranges') and the 20-per-call cap, which signals a lightweight name/code lookup rather than a full lab reference resource. There is no explicit statement of when to use this versus a sibling tool, or of what to do if the term yields no matches.

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