Skip to main content
Glama
Sign In

Medical Terminologies MCP

by io.github.SidneyBissoli
OverviewDiscussionsAdmin

LOINC Code Details

loinc_details
Read-onlyIdempotent

Get detailed information about a specific LOINC code.

Use this tool to:

  • Get the full name and description of a LOINC code

  • Find the component, property, timing, and system

  • Check the scale type and method

Provide a LOINC number in format "XXXXX-X" (e.g., "2339-0" for Glucose).

Input Schema

NameRequiredDescriptionDefault
loinc_numYesLOINC number (e.g., "2339-0")

Output Schema

NameRequiredDescriptionDefault
classYesLOINC class the term is grouped under (e.g. "CHEM").
statusYesLOINC term status (e.g. "ACTIVE", "DEPRECATED"); empty when the source omits it.
systemYesLOINC axis 4, System: the specimen or thing observed (e.g. "Bld", "Ser/Plas").
propertyYesLOINC axis 2, Property: the kind of quantity (e.g. "MCnc" = mass concentration).
componentYesLOINC axis 1, Component: what is measured or observed (e.g. "Glucose").
loinc_numYesLOINC number (e.g. "2339-0").
provenanceYesProvenance block: source, URL, data vintage, extraction instant, origin diagnostics, citation, license
scale_typeYesLOINC axis 5, Scale: Qn (quantitative), Ord, Nom, Nar, etc.
short_nameYesLOINC short name; empty when the source has none.
attributionYesCanonical source URLs of this response (attribution list)
method_typeYesLOINC axis 6, Method; empty when the term specifies none.
time_aspectYesLOINC axis 3, Time: point in time or interval of the observation (e.g. "Pt", "24H").
long_common_nameYesLOINC Long Common Name, the full human-readable name of the term.
external_copyright_noticeYesThird-party copyright notice the term carries, served verbatim (LOINC License §10); null when it carries none.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • addedOutput schema / properties / class / description
      Added value: +"LOINC class the term is grouped under (e.g. \"CHEM\")."
    • addedOutput schema / properties / component / description
      Added value: +"LOINC axis 1, Component: what is measured or observed (e.g. \"Glucose\")."
    • addedOutput schema / properties / external_copyright_notice / description
      Added value: +"Third-party copyright notice the term carries, served verbatim (LOINC License §10); null when it carries none."
    • addedOutput schema / properties / loinc_num / description
      Added value: +"LOINC number (e.g. \"2339-0\")."
    • addedOutput schema / properties / long_common_name / description
      Added value: +"LOINC Long Common Name, the full human-readable name of the term."
    • addedOutput schema / properties / method_type / description
      Added value: +"LOINC axis 6, Method; empty when the term specifies none."
    • addedOutput schema / properties / property / description
      Added value: +"LOINC axis 2, Property: the kind of quantity (e.g. \"MCnc\" = mass concentration)."
    • addedOutput schema / properties / scale_type / description
      Added value: +"LOINC axis 5, Scale: Qn (quantitative), Ord, Nom, Nar, etc."
    • addedOutput schema / properties / short_name / description
      Added value: +"LOINC short name; empty when the source has none."
    • addedOutput schema / properties / status / description
      Added value: +"LOINC term status (e.g. \"ACTIVE\", \"DEPRECATED\"); empty when the source omits it."
    • addedOutput schema / properties / system / description
      Added value: +"LOINC axis 4, System: the specimen or thing observed (e.g. \"Bld\", \"Ser/Plas\")."
    • addedOutput schema / properties / time_aspect / description
      Added value: +"LOINC axis 3, Time: point in time or interval of the observation (e.g. \"Pt\", \"24H\")."
  2. Changed1 schema field changed
    • changedOutput schema / properties / provenance / properties / notices / description
      Previous value: -"Notices the source publishes alongside the data (license statements, caveats), verbatim. Absent when there is none"New value: +"Caveats the source publishes about the data, verbatim (license statements are not repeated here; see the info://licenses resource). Absent when there is none"
  3. Changed7 schema fields changed
    • changedOutput schema / properties / provenance / description
      Previous value: -"Provenance block (contract v1.1): source, URL, data vintage, extraction instant, origin diagnostics, citation, license"New value: +"Provenance block: source, URL, data vintage, extraction instant, origin diagnostics, citation, license"
    • addedOutput schema / properties / provenance / properties / derivation_note
      Added value: +{
+  "description": "What this server computed; present together with derived",
+  "type": "string"
+}
    • addedOutput schema / properties / provenance / properties / derived
      Added value: +{
+  "description": "Present (true) only when this server computed the value (e.g. a ranking or summary statistics) instead of passing on what the source returned",
+  "type": "boolean"
+}
    • changedOutput schema / properties / provenance / properties / field_sources / description
      Previous value: -"Present only when the response joins parts from different origins or extraction instants (contract v1.2): for each group of fields, its URL, extraction instant and whether it came from cache. Absent in single-origin responses"New value: +"Present only when the response joins parts from different origins or extraction instants: for each group of fields, its URL, extraction instant and whether it came from cache. Absent in single-origin responses"
    • addedOutput schema / properties / provenance / properties / notices
      Added value: +{
+  "description": "Notices the source publishes alongside the data (license statements, caveats), verbatim. Absent when there is none",
+  "items": {
+    "type": "string"
+  },
+  "minItems": 1,
+  "type": "array"
+}
    • changedOutput schema / properties / provenance / properties / retrieval / description
      Previous value: -"Origin diagnostics of THIS source in this call (contract v1.1): requests made to the upstream, attempts summed across retries, anomalies worked around (kind + count); unstable=true when any anomaly happened. null when nothing was measured (bundled dataset, or response served entirely from cache)"New value: +"Origin diagnostics of THIS source in this call: requests made to the upstream, attempts summed across retries, anomalies worked around (kind + count); unstable=true when any anomaly happened. null when nothing was measured (bundled dataset, or response served entirely from cache)"
    • addedOutput schema / properties / provenance / properties / revision
      Added value: +{
+  "additionalProperties": false,
+  "description": "Whether the data can still change at the source: current = the version in force, the source may revise it; provisional = preliminary; final = will not change. Absent when unknown",
+  "properties": {
+    "note": {
+      "description": "O específico da fonte: o que revisa, quando, por quê",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "status": {
+      "description": "current = versão vigente, a fonte pode revisá-la; provisional = preliminar, incompleta ou sujeita a mudança (não compare como se fosse fechada); final = não muda mais, declarado pela fonte",
+      "enum": [
+        "current",
+        "provisional",
+        "final"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "note"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedOutput schema / properties / provenance / properties / field_sources
      Added value: +{
+  "description": "Present only when the response joins parts from different origins or extraction instants (contract v1.2): for each group of fields, its URL, extraction instant and whether it came from cache. Absent in single-origin responses",
+  "items": {
+    "additionalProperties": false,
+    "description": "Proveniência de um grupo de campos da resposta: de onde veio e quando foi extraído",
+    "properties": {
+      "data_vintage": {
+        "description": "Vintage/competência da sub-fonte",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "dataset_id": {
+        "description": "Identificador do conjunto da sub-fonte",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "fields": {
+        "description": "Campos do payload atribuídos a esta sub-fonte",
+        "items": {
+          "type": "string"
+        },
+        "minItems": 1,
+        "type": "array"
+      },
+      "retrieved_at": {
+        "description": "ISO-8601 da extração desta sub-fonte na origem",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "served_from_cache": {
+        "description": "true se esta sub-fonte veio do cache do servidor (retrieved_at é o da extração original); false se foi buscada nesta chamada; null se o servidor não distingue",
+        "type": [
+          "boolean",
+          "null"
+        ]
+      },
+      "source_url": {
+        "description": "URL canônica da sub-fonte que originou estes campos",
+        "type": "string"
+      }
+    },
+    "required": [
+      "fields",
+      "source_url",
+      "dataset_id",
+      "data_vintage",
+      "retrieved_at"
+    ],
+    "type": "object"
+  },
+  "minItems": 1,
+  "type": "array"
+}
  5. Changed3 schema fields changed
    • changedOutput schema / properties / provenance / description
      Previous value: -"Provenance block (contract v1.0): source, URL, data vintage, extraction instant, citation, license"New value: +"Provenance block (contract v1.1): source, URL, data vintage, extraction instant, origin diagnostics, citation, license"
    • addedOutput schema / properties / provenance / properties / retrieval
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "anomalies": {
+          "description": "Anomalias superadas até o sucesso, somadas por classe, em ordem fixa; [] se nenhuma",
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "count": {
+                "description": "Ocorrências desta classe na chamada",
+                "maximum": 9007199254740991,
+                "minimum": 1,
+                "type": "integer"
+              },
+              "kind": {
+                "description": "Classe da anomalia (vocabulário fechado do contrato)",
+                "enum": [
+                  "timeout",
+                  "network",
+                  "http_4xx",
+                  "http_5xx",
+                  "rate_limited",
+                  "malformed_body"
+                ],
+                "type": "string"
+              }
+            },
+            "required": [
+              "kind",
+              "count"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "attempts": {
+          "description": "Tentativas somadas, incluindo as repetidas (>= requests)",
+          "maximum": 9007199254740991,
+          "minimum": 1,
+          "type": "integer"
+        },
+        "requests": {
+          "description": "Idas distintas à origem que compõem esta resposta (fatias, páginas)",
+          "maximum": 9007199254740991,
+          "minimum": 1,
+          "type": "integer"
+        },
+        "unstable": {
+          "description": "true se houve repetição (attempts > requests) ou alguma anomalia",
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "requests",
+        "attempts",
+        "anomalies",
+        "unstable"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Origin diagnostics of THIS source in this call (contract v1.1): requests made to the upstream, attempts summed across retries, anomalies worked around (kind + count); unstable=true when any anomaly happened. null when nothing was measured (bundled dataset, or response served entirely from cache)"
+}
    • changedOutput schema / properties / provenance / required
      Previous value: -[
-  "source",
-  "source_url",
-  "data_vintage",
-  "retrieved_at",
-  "citation",
-  "license"
-]New value: +[
+  "source",
+  "source_url",
+  "data_vintage",
+  "retrieved_at",
+  "retrieval",
+  "citation",
+  "license"
+]
  6. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  7. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, open-world, and non-destructive, so the safety profile is fully covered. The description adds the shape of the returned record (component, property, timing, system, scale, method), but since an output schema exists this largely restates structured data; nothing is said about behavior for unknown or malformed codes.

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?

Short, front-loaded, and scannable with a bulleted capability list followed by the input format note. The only slack is the format sentence, which repeats the schema's example.

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 rich annotations, a fully documented single parameter, and an output schema, the definition covers what an agent needs to call it correctly. Missing only the relationship to loinc_search and any error behavior for invalid codes.

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% and the schema already provides the pattern and the '2339-0' example. The description's format note ('XXXXX-X', Glucose example) duplicates that, so it adds no semantics beyond the schema.

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 ('Get detailed information about a specific LOINC code'), which is unambiguous. However, it never distinguishes itself from siblings like loinc_search, loinc_answers, or loinc_panels, so the agent must infer that this is the lookup-by-identifier path.

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?

The bulleted 'Use this tool to' list implies usage when you already hold a LOINC number, but it names no alternatives and gives no exclusion criteria. The sibling loinc_search is the obvious companion (find a code, then detail it) and is never mentioned.

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

All Medical Terminologies MCP toolsInspect
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.

Resources