Skip to main content
Glama
Ada MCP Server

Ada MCP Server

ada_get_spec

Find the Ada specification (.ads) matching a given body file (.adb), with optional line and column for precise lookup.

Instructions

Navigate from body to spec file, or find corresponding spec

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>"
    },
    "name": "ada_get_spec"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesAbsolute path to the Ada file (usually .adb)
lineNoOptional 1-based line number for precise lookup
columnNoOptional 1-based column number for precise lookup

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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 discloses almost nothing: it does not state that this is a read-only lookup, what happens when no spec exists (e.g. a body with no visible spec), or whether it searches the project or only the local directory. The line/column parameters suggest position resolution, but the description never explains what behavior they change.

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 short sentence with the primary action front-loaded and no filler. The only inefficiency is that the two clauses overlap rather than each contributing new information.

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

Completeness2/5

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

There is no output schema, so the description should indicate what comes back — a file path, a position, a list of candidates, or an empty result when no spec exists — and it says nothing. For a navigation tool whose whole value is the returned mapping, an agent cannot predict the response shape or failure mode from this definition.

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 already documented, including the 'usually .adb' hint and 1-based line/column semantics. The description adds no meaning beyond that, which is the expected baseline when the schema does the work.

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 and resource: navigating between an Ada body file and its corresponding spec file, which is a distinct operation from siblings like ada_goto_definition or ada_find_references. It stops short of saying whether the reverse direction (spec to body) is supported, and the second clause ('or find corresponding spec') largely restates the first.

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 implied by the domain: use this when you have an Ada file and want its spec counterpart. No alternatives are named, so an agent must infer on its own why it would pick this over ada_goto_definition or ada_find_references when the goal is locating a declaration.

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