Skip to main content
Glama
Hollway

mcp-abap-abap-adt-api

by Hollway
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

deleteMethod

Destructive

Removes an ABAP method's declaration and implementation from a class. Safely handles METHODS chains and supports dry-run previews and usage checks before activation.

Instructions

Remove a method from a class - both its declaration and its implementation - and activate. A declaration inside a METHODS: chain is handled: the entry goes, and if it was the last one the chain is closed so it still compiles. What it will not do is guess at a line that declares two methods at once; that is refused and named, because rewriting it wrong takes somebody else's method with it. Pass dryRun to see the diff first, and check usageReferences before removing a method that anything calls.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dryRunNoShow the diff without locking or writing.
activateNoActivate afterwards (default true).
classNameYesClass name, e.g. ZCL_APP.
transportNoTransport request for the change.
methodNameYesMethod to remove.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description adds valuable context: handling of METHODS: chains, refusal of ambiguous multi-method lines, and the dryRun behavior. This goes beyond the annotation's simple destructiveness flag, but does not cover every possible edge case.

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?

Four sentences with zero waste. The core purpose is front-loaded, followed by edge-case handling and usage cautions. Every sentence earns its place, making it highly scannable for an agent.

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

Completeness4/5

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

Given the 5 parameters (2 required), no output schema, and annotations covering safety, the description is complete for correct invocation. It explains the main behavior, edge cases, and provides a dryRun option. Minor gaps like return format are not required since no output schema exists.

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% with all parameters described. The description reinforces dryRun's purpose ('see the diff') but adds little semantic meaning beyond the schema. Baseline 3 is appropriate as the schema already carries the parameter definitions.

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 states a specific verb (Remove), a resource (method from a class), and scope (both declaration and implementation, plus activation). It clearly distinguishes from siblings like addMethod (adds) and deleteObject (deletes an object), leaving no ambiguity about what this tool does.

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?

Provides explicit guidance to use dryRun to preview the diff and to check usageReferences before removal. It implies when to use the tool (removing methods) and cautions about edge cases, though it does not name alternative tools explicitly.

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

Deploy Server

Other Tools