Skip to main content
Glama

Resolve HPO Term

resolve_term
Read-onlyIdempotent

Resolve phenotype labels, synonyms, HP IDs, or external cross-references to canonical HPO terms, handling ambiguous queries and obsolete IDs with replacement suggestions.

Instructions

Resolve a phenotype label, synonym, HP id (HP:0000118), or external cross-reference CURIE (UMLS:C0036572, SNOMEDCT_US:193046000, ...) to the canonical HPO term {hpo_id, name, match_type}. An ambiguous label returns ambiguous_query with candidates; an obsolete HP id returns not_found with its successor in replaced_by. This is the recommended first step — resolve any query to a canonical HP id before calling get_term. Signature: resolve_term(query, response_mode=).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesA phenotype label, synonym, HP id (HP:0000118), or external xref CURIE (UMLS:C0036572, SNOMEDCT_US:193046000, ...).
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
queryNo
hpo_idNo
nameNo
match_typeNo
obsoleteNo
hpo_versionNo
recommended_citationNo
Behavior5/5

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

Beyond annotations (readOnly, idempotent), the description details behavior for ambiguous labels (returns candidates) and obsolete IDs (returns replaced_by), adding significant value.

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 plus a signature line, no fluff, front-loaded with purpose and followed by crucial details.

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 output schema exists, the description adequately covers return structure, special cases, and parameter verbosity, making it complete for a resolver tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage, the description explains the query parameter with examples and lists response_mode enum values and default, adding meaning beyond the schema.

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 resolves various inputs to a canonical HPO term, distinguishes from siblings like 'search_terms' and 'resolve_xref', and mentions specific cases (ambiguous, obsolete).

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 explicitly recommends it as the first step before calling 'get_term', and explains handling of ambiguous and obsolete queries, though it doesn't explicitly state when not to use it.

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