Skip to main content
Glama

Look Up Reference Range

lookup-reference-range
Read-onlyIdempotent

Typical reference ranges for a lab marker (e.g. TSH, ferritin, LDL cholesterol, vitamin D), optionally by sex and age, with unit, source and the JustLabs test that measures it. Educational only: ranges vary by lab and method, and the range printed on the patient's own lab report applies. Product terms only — send the marker name, never a result value, name, date of birth or other personal details. It does not interpret results.

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": {
      "marker": "<marker>"
    },
    "name": "lookup-reference-range"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageNo
sexNo
markerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, so the description only needs to add context. It adds two useful traits: the output is educational and lab/method-dependent, and inputs must be product terms with no PII — a real privacy constraint an agent would otherwise not know. It does not say how an unknown marker or an omitted sex/age is handled.

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 definition is front-loaded with what the tool returns, then caveats, then input constraints — a sensible order with no filler. The educational disclaimer is slightly wordy but each clause adds distinct meaning (lab variability, the patient's own report governs).

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?

With no output schema, the description correctly enumerates the returned fields (unit, source, measuring test) and flags that ranges vary by lab and method. Combined with the PII prohibition, an agent has enough to call this safely. The only real gap is fallback behavior for missing sex/age or an unrecognized marker.

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 0%, so the description carries the burden for all three parameters. It clarifies that 'marker' takes a marker name (with examples) and that 'sex' and 'age' are optional refinements of the range. It does not explain what the returned range defaults to when sex or age are omitted, nor any format expectations for marker beyond the schema's length bounds.

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?

The description gives a specific verb+resource ('Typical reference ranges for a lab marker') and concretizes it with example markers (TSH, ferritin, LDL cholesterol, vitamin D) plus the fields returned (unit, source, measuring test). It also draws a boundary by stating 'It does not interpret results.' It never names a sibling tool or explicitly says how it differs from get-test-details, so it stops short of full differentiation.

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?

Usage context is clear: look up a typical range for a named marker, optionally narrowed by sex and age, for educational purposes only. The description also states negative guidance — do not send result values or personal details, and it does not interpret results. It does not point to any alternative sibling when a caller actually wants interpretation or test details.

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