Skip to main content
Glama
Ada MCP Server

Ada MCP Server

ada_implementation

Finds the implementation body for an Ada declaration or specification at a given file, line, and column so you can jump from spec to code.

Instructions

Navigate from declaration to implementation (spec to body)

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

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

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and does not meet it. It never states that the operation is read-only, nor what happens when no implementation body exists (empty result, error, null), nor that the file/line/column must point at a declaration rather than a usage.

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 short phrase with the direction of navigation front-loaded and no filler. For a three-parameter navigation tool this is appropriately sized, though the terseness is partly why other dimensions score lower.

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?

The tool is conceptually simple and the description conveys the core jump direction, which is the minimum needed to call it. However, with no output schema and no annotations, the definition leaves the result shape and the no-implementation-found case entirely unspecified.

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% and the schema already documents that file is an absolute path and line/column are 1-based, so the baseline is 3. The description adds only a mild hint that the position should be a declaration ('from declaration'), without expanding on coordinate semantics.

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?

States a specific verb+resource pair (navigate from declaration to implementation) and clarifies direction with '(spec to body)', so an agent knows it is jumping downward from a spec to its body. It does not explicitly distinguish itself from the closely related ada_goto_definition or ada_get_spec siblings, which keeps it short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied: the parenthetical '(spec to body)' suggests calling it while positioned on a package spec declaration. There is no explicit statement of when to prefer it over ada_goto_definition or ada_get_spec, and no exclusion for positions that are not declarations.

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