Skip to main content
Glama
Ada MCP Server

Ada MCP Server

ada_completions

Get code completion suggestions at a specific line and column in an Ada file, helping you resolve incomplete Ada code and choose valid symbols as you edit.

Instructions

Get code completion suggestions at a position in an Ada file

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

Input Schema

NameRequiredDescriptionDefault
fileYesAbsolute path to the Ada file
lineYes1-based line number
limitNoMaximum number of completions to return
columnYes1-based column number
trigger_characterNoTrigger character (e.g., '.', ':')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 disclosure burden, yet it says nothing about whether this is a read-only operation, what happens on invalid positions or unparsable files, or how many results come back by default. The only behavioral hint is the schema default of limit=50, which is structured data rather than description content.

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 compact sentence that front-loads the action and the locational constraint with no filler. Its brevity is close to optimal, though the space saved could have been used for the missing differentiation and behavioral notes.

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?

With five parameters (three required), no annotations, and no output schema, the definition is minimally adequate: the schema covers the inputs fully, but the description does not indicate what a completion item looks like or how to interpret an empty result. For a tool with no annotation and no return-value documentation, more context would help.

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 every parameter including file, line, column, limit, and trigger_character is already documented in the schema. The description adds no meaning beyond it, which matches the baseline 3 when the schema does the heavy lifting.

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 and resource ('Get code completion suggestions') plus the scoping detail 'at a position in an Ada file', which tells an agent exactly what the call produces. It does not, however, distinguish itself from related siblings such as ada_signature_help or ada_hover, which could also apply at a cursor position.

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 explicit guidance on when to use this tool versus alternatives like ada_signature_help or ada_hover, and no prerequisites are mentioned. Usage is only implied by the phrase 'at a position', leaving the agent to infer the choice among position-based sibling tools.

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