Skip to main content
Glama

map_loinc_to_snomed

Read-onlyIdempotent

Enter a LOINC code to get guidance on where to find LOINC to SNOMED CT mappings.

Instructions

This tool looks up a LOINC code in NLM Clinical Tables and returns guidance on where to obtain a LOINC → SNOMED CT mapping. It does not perform the mapping.

Direct LOINC → SNOMED CT mappings are not freely available via API. UMLS Metathesaurus contains the relationships but requires an individual UMLS Terminology Services license; the LOINC SNOMED CT Expression Association is published by Regenstrief Institute as part of the LOINC release and requires authenticated download from loinc.org under the LOINC license.

For programmatic LOINC → SNOMED mapping, use UMLS or the LOINC Expression Association files. For interactive lookup, use the SNOMED CT browser available to your organization or the Regenstrief RELMA desktop tool.

Provide a LOINC code like "2339-0" (Glucose) or "718-7" (Hemoglobin).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
loinc_codeYesLOINC code (e.g., 2339-0 for Glucose)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
loinc_codeYesThe LOINC code as submitted.
loinc_detailsYesNLM Clinical Tables details for the LOINC code (component, system, property, etc.). Null when the code was not found upstream.
statusYesAlways "guidance-only" — direct LOINC → SNOMED CT mappings require licensed sources (UMLS Metathesaurus or LOINC SNOMED CT Expression Association). This tool returns pointers, not the mapping itself.
guidanceYesShort human-readable explanation of why this tool returns guidance instead of a mapping.
mapping_sourcesYesStructured list of authoritative LOINC → SNOMED CT mapping sources (UMLS Metathesaurus, LOINC SNOMED CT Expression Association, Regenstrief RELMA).
Behavior5/5

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

All annotations (readOnly, idempotent, openWorld) are consistent with the description's statements that the tool is a safe lookup providing guidance. The description adds behavioral details about licensing and access restrictions, going beyond annotations.

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?

Three paragraphs, but every sentence adds information. Front-loaded with the essential point (guidance, not mapping). Could be slightly more streamlined, but it is efficient for the complexity.

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?

Given the output schema exists, no need to describe return format. The description covers purpose, limitations, licensing, alternatives, and parameter usage thoroughly. Fully adequate for a lookup tool with rich annotations.

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 100% with a clear description for loinc_code. The description reinforces the format with examples (2339-0, 718-7), adding value. Baseline 3, but the examples and extra context justify a 4.

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?

The description explicitly states the tool looks up a LOINC code and returns guidance on obtaining a mapping, not performing the mapping itself. This verb+resource is specific and distinguishes it from sibling tools like map_icd10_to_icd11.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit when-to-use (lookup guidance) and when-not-to-use (does not perform mapping), and names alternatives like UMLS, LOINC Expression Association, SNOMED CT browser, and RELMA. This gives clear context for tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SidneyBissoli/medical-terminologies-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server