Skip to main content
Glama
Ada MCP Server

Ada MCP Server

ada_call_hierarchy

Retrieves incoming and outgoing call hierarchy for an Ada symbol at a given file position. Use it to trace callers and callees for code navigation and impact analysis.

Instructions

Get call hierarchy (incoming/outgoing calls) for an Ada symbol

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": {
      "file": "<file>",
      "line": "<line>",
      "column": "<column>"
    },
    "name": "ada_call_hierarchy"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesAbsolute path to the Ada file
lineYes1-based line number
columnYes1-based column number
directionNoCall direction: 'outgoing', 'incoming', or 'both'outgoing

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden; the verb "Get" does make clear this is a read-only lookup with no mutation risk. However, it says nothing about traversal depth, result size/truncation, or whether the hierarchy is a single-level expansion, which matters for a hierarchy tool with no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the core action and scope come first. It is efficient, though it is on the terse side given the tool's behavioral complexity.

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?

For a 4-parameter read tool with no annotations and no output schema, the definition covers what the tool does but not what it returns (a call tree/edge list) or its limits. An agent could invoke it correctly thanks to the fully documented schema, but would not know what to expect back.

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 four parameters including the direction enum and 1-based line/column conventions are already documented. The description only restates "incoming/outgoing," adding no syntax or meaning beyond the schema — the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb+resource ("Get call hierarchy") and clarifies the scope with "(incoming/outgoing calls) for an Ada symbol," which distinguishes it from a plain references lookup. It does not explicitly name a sibling such as ada_find_references or ada_dependency_graph, so an agent must infer the boundary itself.

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?

There is no when-to-use or when-not-to-use guidance: nothing says to prefer this over ada_find_references for plain usages or over ada_dependency_graph for module-level structure. The parenthetical hints at the shape of the result but not the selection criteria.

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