Skip to main content
Glama
Ada MCP Server

Ada MCP Server

ada_type_definition

Navigate from an Ada object or parameter identifier to its type declaration to inspect the defining type. Use this to resolve inferred types and jump to the relevant type definition.

Instructions

Navigate from an object or parameter identifier to its type declaration; use ada_goto_definition on an explicit type name

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_type_definition"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesAbsolute path to the Ada file
lineYes1-based line number
columnYes1-based column number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden alone. 'Navigate' implies a read-only lookup, but the description never says whether the result is a returned location, a list of declarations, or an editor jump, so the agent cannot anticipate the response shape. For a simple LSP navigation call, that gap is acceptable but real.

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?

A single sentence split by a semicolon: the capability comes first and the sibling routing comes second. There is no padding, and no sentence could be removed without losing information.

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?

For a three-parameter, fully documented, read-only navigation tool, the definition covers the trigger decision adequately. The only material omission is what the call returns, which matters more here because there is no output schema.

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 coverage is 100%, so all three parameters are documented in the schema, which sets the baseline at 3. The phrase 'from an object or parameter identifier' implicitly constrains what the file/line/column position must point at, which adds modest value over the schema's generic '1-based line number' wording.

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?

States a precise verb and a precise source-and-target pair: 'Navigate from an object or parameter identifier to its type declaration.' This separates it cleanly from ada_goto_definition, which the description explicitly names as the alternative for an explicit type name.

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?

Gives the selecting condition for the sibling: use ada_goto_definition when you have an explicit type name, which implies this tool is for when the cursor is on a variable or parameter. The description doesn't spell out the exclusion in both directions, but the routing choice is clear.

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