Skip to main content
Glama
fr0ster

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

UpdateInterface

Modify the source code of an existing ABAP interface. Handles locking, updating, unlocking, and optional activation.

Instructions

Update source code of an existing ABAP interface. Locks, updates, unlocks, and optionally activates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
detailNoHow much of the answer to return: "terse" (default, the fields you need to act), "full" (the whole parse), "raw" (the document as ADT sent it).terse
activateNoActivate interface after update. Default: true.
source_codeYesComplete ABAP interface source code with INTERFACE...ENDINTERFACE section.
interface_nameYesInterface name. Must exist in the system.
transport_requestNoTransport request number, not a task. Optional if object is local or already in transport.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv16.0.0
    • addedInput schema / properties / detail
      Added value: +{
+  "default": "terse",
+  "description": "How much of the answer to return: \"terse\" (default, the fields you need to act), \"full\" (the whole parse), \"raw\" (the document as ADT sent it).",
+  "enum": [
+    "terse",
+    "full",
+    "raw"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / interface_name / description
      Previous value: -"Interface name (e.g., ZIF_MY_INTERFACE). Must exist in the system."New value: +"Interface name. Must exist in the system."
    • changedInput schema / properties / transport_request / description
      Previous value: -"Transport request number (e.g., E19K905635). Optional if object is local or already in transport."New value: +"Transport request number, not a task. Optional if object is local or already in transport."
  2. First observed

TDQS

A4/5.0
Behavior4/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. It discloses the internal sequence (locks, updates, unlocks, optionally activates), which is important context beyond the schema and indicates state changes. It does not mention permission requirements, concurrency behavior, or failure modes. Given the absent annotations and the mutation nature, this is a solid but incomplete disclosure.

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?

A single, dense sentence that front-loads the main action and then lists the operational steps; no filler or redundant restatement of the name. Efficient and complete.

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?

For a mutation tool with no annotations and no output schema, the description covers the essential lifecycle (lock-update-unlock-activate) and distinguishes from siblings reasonably well. It could be stronger with explicit prerequisites or error behavior, but it meets the needs 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 schema already documents each parameter, including default values for activate and detail. The description adds no new parameter-level information. Baseline 3 is appropriate when structured fields are complete.

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?

Specific verb (Update) and resource (source code of an existing ABAP interface). The sibling set contains GetInterface, CreateInterface, DeleteInterface, and ActivateInterface, so 'Update source code' cleanly distinguishes this from get/create/delete/activate.

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

Usage Guidelines3/5

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

The description implies the tool is for modifying existing interfaces (interface_name must exist). However, it does not tell the agent when to use UpdateInterface vs ActivateInterface (especially since activate defaults to true) or when to use DeleteInterface. Some guidance is implied by 'existing', but no explicit alternatives are named.

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