Skip to main content
Glama

Get HPO Term Descendants

get_term_descendants
Read-onlyIdempotent

Retrieve all specific descendant phenotype terms of an HPO term using transitive is_a hierarchy, with pagination support for large result sets.

Instructions

Return all transitive is_a descendants (more specific 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_children for only the immediate children. Signature: get_term_descendants(term, limit=, offset=, response_mode=).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYesAn HP id (HP:0000118), a phenotype label/synonym, or an external xref CURIE that resolves to a single HPO term.
limitNoMax rows returned (default 50).
offsetNoRows to skip for forward paging (default 0).
response_modeNoVerbosity: minimal|compact|standard|full (default compact).compact

Output Schema

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

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. Description adds that it uses a 'precomputed closure' and details pagination behavior (truncated, next_offset). No contradictions.

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?

Two sentences, no wasted words. First sentence covers main functionality and pagination, second provides sibling differentiation and signature.

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 (pagination block) and full schema coverage of parameters, description is complete. It explains pagination, alternative tool, and parameter 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 value by summarizing the signature and explaining the pagination block structure beyond 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 explicitly states the verb 'Return' and the resource 'transitive is_a descendants of an HPO term', and distinguishes itself with 'Use get_term_children for only the immediate children.'

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?

Provides explicit guidance on when to use this tool vs. the sibling 'get_term_children', and explains pagination handling with next_offset 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