Skip to main content
Glama
Sign In
Understand-Anything MCP Server

Understand-Anything MCP Server

by VIethoangnguyenle
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_class_hierarchy

Display the inheritance hierarchy for a class, showing all parent and child classes and their extends/implements relations.

Instructions

Show the inheritance hierarchy for a class (extends/implements tree).

Args: class_id: Class node ID to analyze. direction: "up" (parents/supertypes), "down" (children/subtypes), "both". max_depth: Max traversal depth (default 5, max 10). project: Project name.

Returns: Inheritance tree showing parent and child classes with relation types.

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": {
      "class_id": "<class_id>"
    },
    "name": "get_class_hierarchy"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectNo
class_idYes
directionNoboth
max_depthNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the return type ('Inheritance tree showing parent and child classes with relation types') but does not mention error behavior, performance implications, or any side effects. This is acceptable for a simple read-only query but lacks richer context.

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 well-structured with a one-line purpose, a concise parameter list, and a return value note. Every sentence earns its place with no redundancy.

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

Completeness4/5

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

The description covers the core functionality, parameters, and return value. It lacks usage guidance and edge-case behavior, but the presence of an output schema reduces the need to explain return details in prose, making it reasonably complete.

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?

The schema has 0% description coverage, so the description compensates by explaining each parameter in the Args section, including direction values, max_depth limits, and project name. This adds meaning beyond the schema, though the 'project' parameter could be described more fully.

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's function with a specific verb and resource: 'Show the inheritance hierarchy for a class (extends/implements tree).' This distinguishes it from sibling tools like get_relationships or get_node_detail, which are more generic.

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 explicit guidance is provided on when to use this tool versus alternatives. The description only explains what it does, leaving the agent to infer its use case from the purpose and parameter names.

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