Skip to main content
Glama
Ada MCP Server

Ada MCP Server

ada_code_actions

Retrieves available quick fixes and refactorings for a selected Ada code range, helping identify actions to resolve issues or improve code.

Instructions

Get available code actions (quick fixes, refactorings) for a range

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>",
      "start_line": "<start_line>",
      "start_column": "<start_column>"
    },
    "name": "ada_code_actions"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesAbsolute path to the Ada file
end_lineNoEnd line number (1-based), defaults to start_line
end_columnNoEnd column number (1-based), defaults to start_column
start_lineYesStart line number (1-based)
start_columnYesStart column number (1-based)

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 provided, so the description carries the full burden. "Get" implies a read, but the description never confirms this is non-mutating, never says whether actions are merely listed versus applied, and never notes that the result may be empty when no fixes are available at the range.

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, and the key resource and scope come first. It is arguably too terse given the tool's complexity, but nothing is wasted or buried.

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?

With five parameters, no annotations, and no output schema, the description should explain the return shape (a list of action titles/kinds) and how those actions are subsequently applied. It leaves the agent unsure whether invoking it performs a refactor or just reports candidates, which matters for a code-fixing tool.

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 line/column and file semantics are fully documented in the schema itself. The description adds only the notion of a "range", which the start/end parameter descriptions already convey; the baseline 3 is appropriate.

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?

"Get available code actions (quick fixes, refactorings) for a range" gives a specific verb, resource, and scope, and the parenthetical names the action categories. It is clear what the tool returns, though it does not differentiate itself from siblings such as ada_diagnostics or ada_rename_symbol, which overlap with quick fixes and refactorings.

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 statement of when to use this tool versus alternatives, no prerequisite that a range be on/near a diagnostic or symbol, and no note on what to do with the results afterward. The agent must infer usage entirely from the tool name and the word "range".

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