Skip to main content
Glama
Sign In
mcp-ubergraph-query

mcp-ubergraph-query

by twhetzel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_hierarchy

Retrieve hierarchical relationships (parents, children, ancestors, descendants) for an ontology term using its CURIE, with configurable traversal depth.

Instructions

Get hierarchical relationships for a term (parents, children, ancestors, descendants).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "curie": "<curie>"
    },
    "name": "get_hierarchy"
  }
}

Input Schema

NameRequiredDescriptionDefault
curieYesOntology term CURIE
relationNoType of relationship to retrieveparents
depthNoHow many levels to traverse (1-5)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It only states 'get hierarchical relationships' without explaining return format, pagination, or whether data is read-only. No behavioral traits beyond the schema are revealed.

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?

The description is a single, front-loaded sentence that directly conveys the tool's purpose. No unnecessary words or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

While the tool is simple with 3 params fully described, the description lacks context on default behavior (relation defaults to 'parents', depth to 1) and expected output structure. With no output schema, more context would help, but it is minimally adequate.

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 description coverage is 100%, so all parameters are already documented. The description adds no extra semantic detail beyond what's in the schema (e.g., default depth, effect of relation values). Baseline 3 is appropriate.

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 retrieves hierarchical relationships for a term, listing the specific types (parents, children, ancestors, descendants). It distinguishes from sibling tools (get_term_info, query_ubergraph, search_terms) by focusing on hierarchy navigation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives, such as get_term_info for metadata or query_ubergraph for complex graph queries. The description lacks context on typical use cases or exclusions.

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

Deploy Server

Other Tools