searchloinc
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOINC_PASSWORD | Yes | Your LOINC password from free registration on loinc.org | |
| LOINC_USERNAME | Yes | Your LOINC username from free registration on loinc.org | |
| SEARCHLOINC_RAW_JSON | No | Debug-only flag to enable raw JSON output |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_loincsA | Search LOINC terms (observations/measurements — the main LOINC table). Use this for lab tests, vital signs, clinical measurements, panels, and surveys — anything you'd look up by a test name like 'hemoglobin', 'sodium serum', or a LOINC number. Results are relevance-ranked by the LOINC Search API (same ranking as the loinc.org/search UI); if the top hits miss, reformulate the query rather than deep-paging. Rows are compact for triage — call get_loinc(code) to drill into the full record for a specific LOINC. Output is a TOON table capped to a character budget; when truncated, page with |
| search_answerlistsA | Search LOINC answer lists (the enumerated answer sets attached to survey/nominal terms, e.g. smoking-status choices). Use when you need the allowed answers for a term rather than the term itself. Results are relevance-ranked by the LOINC Search API (same ranking as the loinc.org/search UI); if the top hits miss, reformulate the query rather than deep-paging. Rows are compact for triage — call get_loinc(code) to drill into the full record for a specific LOINC. Output is a TOON table capped to a character budget; when truncated, page with |
| search_partsA | Search LOINC parts (the LP-coded building blocks — components, systems, methods, properties — that compose LOINC terms). Use when you need the canonical part behind a concept, or to explore the axis vocabulary. Results are relevance-ranked by the LOINC Search API (same ranking as the loinc.org/search UI); if the top hits miss, reformulate the query rather than deep-paging. Rows are compact for triage — call get_loinc(code) to drill into the full record for a specific LOINC. Output is a TOON table capped to a character budget; when truncated, page with |
| search_groupsA | Search LOINC groups (curated collections of related terms — e.g. all glucose measurements, or a molecular-conversion group). Use when you want a pre-grouped set of related LOINCs rather than individual terms. Results are relevance-ranked by the LOINC Search API (same ranking as the loinc.org/search UI); if the top hits miss, reformulate the query rather than deep-paging. Rows are compact for triage — call get_loinc(code) to drill into the full record for a specific LOINC. Output is a TOON table capped to a character budget; when truncated, page with |
| get_loincA | Drill into one LOINC term by its exact code (e.g. '783-1') and return the full flat record — all populated fields (names, the six-axis parts, related names, ranks, example units, status/change history) plus |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct entity (LOINC term, answer list, group, part) or action (search vs. detail). Descriptions clearly differentiate between them, leaving no ambiguity about which tool to use for a given task.
Tool names follow a consistent verb_noun pattern: 'search_' for searching different entities and 'get_loinc' for fetching details. All names use lowercase and underscores, maintaining a uniform style.
Five tools cover the core functionalities of searching and retrieving LOINC-related data without being excessive. The count is well-scoped for a focused LOINC search server.
The set covers searching for terms, answer lists, groups, and parts, plus detailed term retrieval. However, there is no dedicated detail tool for answer lists or groups; the workflow directs to get_loinc, which may not fully address those entities. This minor gap prevents a perfect score.