Skip to main content
Glama
Ada MCP Server

Ada MCP Server

ada_rename_symbol

Rename an Ada symbol at a given file, line, and column across the entire project, with an optional preview mode that returns changes before applying them.

Instructions

Rename an Ada symbol across the entire project

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

Input Schema

NameRequiredDescriptionDefault
fileYesAbsolute path to the Ada file
lineYes1-based line number
columnYes1-based column number
previewNoIf true, only return changes without applying
new_nameYesNew name for the symbol

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 behavioral burden. It discloses the project-wide blast radius, but never states that it mutates files on disk, whether the change is undoable, that preview defaults to true (a critical safety nuance), or whether failures leave partial edits.

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 zero filler, so it is tight and scannable. It is arguably too terse for a project-wide mutation, but that shortfall is a completeness issue rather than wordiness.

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?

For a five-parameter, mutation-performing tool with no annotations and no output schema, the description omits the essential facts an agent needs: that it writes to files, that preview defaults to true, and what it returns in preview mode. The schema covers parameters, but nothing covers behavior.

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 file, line, column, preview, and new_name are all documented in structured data and the baseline of 3 applies. The description adds no extra meaning, such as whether line/column may point anywhere in an occurrence or only at the declaration.

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 names a specific verb (Rename) and resource (an Ada symbol) plus the scope of effect (across the entire project), which is far clearer than a bare name restatement. It lacks any explicit differentiation from refactor-capable siblings such as ada_code_actions, so an agent cannot rule those out from the description alone.

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 when-to-use or when-not-to-use guidance, no mention of prerequisites (e.g. a loaded project index, or that the position must identify a declaration), and no routing to alternatives like ada_find_references for inspecting impact before renaming.

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