Unofficial HPO MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_hpo_termsB | Search for HPO terms by keyword, ID, or synonym. Supports pagination and filtering. |
| get_hpo_termA | Get detailed information about a specific HPO term by its ID |
| get_all_hpo_termsA | Get a list of all HPO terms with pagination support |
| get_hpo_ancestorsA | Get all ancestor terms for a given HPO term (all terms higher in the hierarchy) |
| get_hpo_parentsA | Get direct parent terms for a given HPO term (one level up in the hierarchy) |
| get_hpo_childrenA | Get direct child terms for a given HPO term (one level down in the hierarchy) |
| get_hpo_descendantsB | Get all descendant terms for a given HPO term (all terms lower in the hierarchy) |
| validate_hpo_idA | Validate if a given string is a valid HPO ID format and check if the term exists |
| get_hpo_term_pathA | Get the full hierarchical path from root to a specific HPO term |
| compare_hpo_termsB | Compare two HPO terms and find their relationship and common ancestors |
| get_hpo_term_statsA | Get comprehensive statistics and analysis for an HPO term including hierarchy counts and properties |
| batch_get_hpo_termsA | Retrieve multiple HPO terms in a single request (maximum 20 terms) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
All tools have clearly distinct purposes: single/batch retrieval, hierarchy navigation (ancestors, parents, children, descendants, path), comparison, search, validation, and statistics. No meaningful overlap.
All tool names follow a consistent verb_noun pattern, predominantly using the prefix 'hpo'. Variations like 'batch_get' vs 'get' are logical and maintain clarity.
12 tools is an appropriate scope for an HPO term server, covering all essential operations without unnecessary bloat or shortage.
The server provides comprehensive coverage for a read-only HPO term service: retrieval, hierarchy traversal, comparison, search, validation, and statistics. There are no obvious gaps for its intended domain.