hpo-link

Overview Schema Source Related Servers Discussions Admin

Get HPO Term

get_term

Read-onlyIdempotent

Retrieve detailed HPO phenotype term records including definition, synonyms, cross-references, and hierarchy. Accepts HP IDs, labels, or external CURIEs.

Instructions

Return an HPO phenotype term record: definition, synonyms (exact/related/broad/narrow), alt_ids, subsets, comments, cross-references, direct parents and children, and obsolescence (replaced_by). The term accepts an HP id, a label/synonym, or an external xref CURIE (resolved first). Pass fields=['synonyms', 'definition'] for a sparse projection. Note on synonyms shape: compact (default) returns synonyms as plain strings; standard/full return {text, scope} objects. Signature: get_term(hpo_id, response_mode=, fields=).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`fields`	No	Sparse fieldset: return ONLY these top-level keys (for map_cross_ontology, dot into the grouped object, e.g. 'mappings.UMLS'). Identity anchors (hpo_id, name, hpo_version) are always included. An unrecognised field is rejected with invalid_input. Omit for the full payload.
`hpo_id`	Yes	Canonical HP id for the resolved HPO term (HP:0000118). Legacy `term` arguments are accepted as an alias.
`response_mode`	No	Verbosity: minimal\|compact\|standard\|full (default compact).	compact

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.4.0Jul 16, 2026

changedInput schema / properties / fields / description

Previous value: -"Sparse fieldset: return ONLY these top-level keys (dot into a grouped object, e.g. 'xrefs.UMLS'). Identity anchors (hpo_id, name, hpo_version) are always included. Omit for the full payload."New value: +"Sparse fieldset: return ONLY these top-level keys (for map_cross_ontology, dot into the grouped object, e.g. 'mappings.UMLS'). Identity anchors (hpo_id, name, hpo_version) are always included. An unrecognised field is rejected with invalid_input. Omit for the full payload."

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": true,
-  "properties": {
-    "_meta": {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    "allowed_values": {
-      "type": "array"
-    },
-    "alt_ids": {
-      "type": "array"
-    },
-    "candidates": {
-      "type": "array"
-    },
-    "children": {
-      "type": "array"
-    },
-    "comments": {
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "kind": {
-            "const": "untrusted_text"
-          },
-          "provenance": {
-            "additionalProperties": false,
-            "properties": {
-              "record_id": {
-                "type": "string"
-              },
-              "retrieved_at": {
-                "type": "string"
-              },
-              "source": {
-                "type": "string"
-              }
-            },
-            "type": "object"
-          },
-          "raw_sha256": {
-            "type": "string"
-          },
-          "text": {
-            "type": "string"
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "definition": {
-      "oneOf": [
-        {
-          "additionalProperties": false,
-          "properties": {
-            "kind": {
-              "const": "untrusted_text"
-            },
-            "provenance": {
-              "additionalProperties": false,
-              "properties": {
-                "record_id": {
-                  "type": "string"
-                },
-                "retrieved_at": {
-                  "type": "string"
-                },
-                "source": {
-                  "type": "string"
-                }
-              },
-              "type": "object"
-            },
-            "raw_sha256": {
-              "type": "string"
-            },
-            "text": {
-              "type": "string"
-            }
-          },
-          "type": "object"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "error_code": {
-      "type": "string"
-    },
-    "field": {
-      "type": "string"
-    },
-    "hint": {
-      "type": "string"
-    },
-    "hpo_id": {
-      "type": "string"
-    },
-    "hpo_version": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "message": {
-      "type": "string"
-    },
-    "name": {
-      "type": "string"
-    },
-    "obsolete": {
-      "type": "boolean"
-    },
-    "parents": {
-      "type": "array"
-    },
-    "recommended_citation": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "recovery_action": {
-      "type": "string"
-    },
-    "retryable": {
-      "type": "boolean"
-    },
-    "subsets": {
-      "type": "array"
-    },
-    "success": {
-      "type": "boolean"
-    },
-    "synonyms": {
-      "items": {
-        "oneOf": [
-          {
-            "type": "string"
-          },
-          {
-            "additionalProperties": true,
-            "properties": {
-              "scope": {
-                "type": "string"
-              },
-              "text": {
-                "type": "string"
-              }
-            },
-            "type": "object"
-          }
-        ]
-      },
-      "type": "array"
-    }
-  },
-  "type": "object"
-}New value: +null

Changed3 schema fields changedv0.3.0Jul 11, 2026

addedOutput schema / properties / comments

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "kind": {
+        "const": "untrusted_text"
+      },
+      "provenance": {
+        "additionalProperties": false,
+        "properties": {
+          "record_id": {
+            "type": "string"
+          },
+          "retrieved_at": {
+            "type": "string"
+          },
+          "source": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "raw_sha256": {
+        "type": "string"
+      },
+      "text": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / definition / oneOf

Added value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "kind": {
+        "const": "untrusted_text"
+      },
+      "provenance": {
+        "additionalProperties": false,
+        "properties": {
+          "record_id": {
+            "type": "string"
+          },
+          "retrieved_at": {
+            "type": "string"
+          },
+          "source": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "raw_sha256": {
+        "type": "string"
+      },
+      "text": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / definition / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

Changed4 schema fields changedv0.1.1Jul 6, 2026

addedInput schema / properties / hpo_id

Added value: +{
+  "description": "Canonical HP id for the resolved HPO term (HP:0000118). Legacy `term` arguments are accepted as an alias.",
+  "examples": [
+    "HP:0000118"
+  ],
+  "type": "string"
+}

removedInput schema / properties / term

Removed value: -{
-  "description": "An HP id (HP:0000118), a phenotype label/synonym, or an external xref CURIE that resolves to a single HPO term.",
-  "examples": [
-    "HP:0000118",
-    "Seizure",
-    "UMLS:C0036572"
-  ],
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "term"
-]New value: +[
+  "hpo_id"
+]

addedOutput schema / properties / synonyms / items

Added value: +{
+  "oneOf": [
+    {
+      "type": "string"
+    },
+    {
+      "additionalProperties": true,
+      "properties": {
+        "scope": {
+          "type": "string"
+        },
+        "text": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  ]
+}

First observedv0.1.0Jun 19, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, etc. The description adds behavioral details like identifier resolution order ('resolved first') and synonym shape variations (compact vs standard/full), which go 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is concise (3 sentences) with no wasted words. Information is front-loaded: first sentence states purpose, subsequent sentences add details on inputs and output shape.

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 no output schema, the description adequately explains return values (definition, synonyms with shape details, always-included anchors) and input flexibility (multiple identifier types and response modes). Covers all key aspects for correct usage.

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%, but description adds significant meaning: explains hpo_id accepts multiple types, fields is for sparse projection, response_mode verbosity levels, and always-included anchors. This enriches the schema definitions.

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 clearly states the tool returns an HPO phenotype term record with specific fields like definition, synonyms, alt_ids, etc. It distinguishes from sibling tools (e.g., get_term_ancestors returns only ancestors) by implying this returns the full term record.

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?

The description explains that the tool accepts various identifier types (HP id, label, synonym, xref) and provides parameter details, but does not explicitly contrast with alternatives like get_term_ancestors. Usage context is implied rather than explicit.

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

Deploy Server

Get HPO Term

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools