Skip to main content
Glama

Get HPO Term Ancestors

get_term_ancestors
Read-onlyIdempotent

Return all broader phenotype ancestors of an HPO term using the precomputed is_a closure, with pagination to handle large result sets.

Instructions

Return all transitive is_a ancestors (broader phenotype terms) of an HPO term via the precomputed closure, with a pagination block {total, returned, limit, offset, truncated, next_offset}. When truncated, next_commands carries a forward-page step (offset) so you can walk a >limit closure without re-sending rows. Use get_term_parents for only the immediate parents. Signature: get_term_ancestors(hpo_id, limit=, offset=, response_mode=).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax rows returned (default 50).
hpo_idYesCanonical HP id for the resolved HPO term (HP:0000118). Legacy `term` arguments are accepted as an alias.
offsetNoRows to skip for forward paging (default 0).
response_modeNoVerbosity: minimal|compact|standard|full (default compact).compact

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hintNo
nameNo
_metaNo
fieldNo
limitNo
totalNo
hpo_idNo
offsetNo
messageNo
successNo
returnedNo
ancestorsNo
retryableNo
truncatedNo
candidatesNo
error_codeNo
hpo_versionNo
next_offsetNo
allowed_valuesNo
recovery_actionNo
Behavior5/5

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

Annotations already indicate readOnly, idempotent, non-destructive. Description adds details about pagination block structure, truncation behavior, and next_offset for forward paging, which is valuable 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?

Three sentences: purpose, pagination detail, sibling alternative. Every sentence adds value, no waste. Front-loaded with essential info.

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 pagination complexity and output schema presence, description covers all needed: what it returns, how to paginate, and when to use sibling. No gaps for agent invocation.

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%, baseline is 3. Description does not add new parameter meaning beyond what schema provides; the schema already includes alias info and enums. The description's mention of signature is redundant.

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?

Clearly states it returns all transitive is_a ancestors (broader phenotype terms) of an HPO term via precomputed closure. Distinguishes from sibling 'get_term_parents' by noting it returns only immediate parents. Verb and resource are specific.

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?

Explicitly tells when to use this tool vs alternatives: 'Use get_term_parents for only the immediate parents.' Also explains pagination with 'next_commands' for walking large closures.

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/berntpopp/hpo-link'

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