mcp-abap-abap-adt-api

renameEvaluate

Read-only

Analyze the symbol at a given position and find its usages to plan a rename without modifying anything.

Instructions

First of the three steps of a rename: it asks the system what the symbol at this position is and where it is used, so the rename can be planned. Nothing is written. Then renamePreview, then renameExecute.

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": {
      "uri": "<uri>",
      "line": "<line>",
      "startColumn": "<startColumn>",
      "endColumn": "<endColumn>"
    },
    "name": "renameEvaluate"
  }
}

Input Schema

Name	Required	Description
`uri`	Yes	The URI of the object to rename.
`line`	Yes	The line number.
`endColumn`	Yes	The ending column.
`startColumn`	Yes	The starting column.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Sep 11, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'Nothing is written.' It adds useful behavioral context by explaining what the tool actually does: resolves the symbol at the position and gathers its usages for planning. This goes beyond the annotation metadata.

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?

Three short sentences, each earning its place: the tool's role in the rename flow, what it does, and the follow-up tools. The key differentiator is front-loaded in the first sentence.

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

Completeness5/5

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

For a simple read-only planning tool with no output schema and no nested objects, the description is complete. It tells the agent what the tool does, that no changes are made, and where it fits in the rename workflow. No additional information is needed for correct invocation.

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 the parameters are already documented. The description adds only the contextual notion that uri/line/startColumn/endColumn identify 'the symbol at this position,' which is helpful but not substantially more than the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the operation: it asks the system to resolve the symbol at a given position and locate its usages to plan a rename. It also distinguishes itself from the sibling tools by positioning itself as the first of the three rename steps, making differentiation trivial.

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

Usage Guidelines4/5

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

The description names the exact sequence — renameEvaluate, then renamePreview, then renameExecute — and notes that nothing is written, which implies it is the safe planning phase. It lacks an explicit when-not-to-use statement, but the step ordering provides strong routing guidance.

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

Deploy Server