abapsmith

abap_write

Read-onlyIdempotent

Create, change, or delete ABAP objects and save, check, or activate them; writes are refused unless ABAP_ALLOW_WRITE=true.

Instructions

Create, change or delete an ABAP object: save/check/activate. LOCKED on this server: ABAP_ALLOW_WRITE does not enable writes, and ABAP_MODE is not set, so that variable is what decides it. Set ABAP_ALLOW_WRITE=true (ABAP_ALLOW_PACKAGES is optional — it narrows the default, which is every package). Calling it returns a refusal and sends nothing to the SAP system.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "abap_write"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.5.6Sep 12, 2026

TDQS

C2.9/5.0

Behavior1/5

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

The description claims create/change/delete operations, but annotations declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, directly contradicting a mutating tool. This is a serious annotation contradiction. The lock/refusal information is useful behavioral context, but the fundamental contradiction dominates.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is somewhat rambling and mixes lock semantics, environment variables, and refusal behavior in a run-on fashion. The core purpose is front-loaded, but the middle sentences are difficult to parse and could be tighter.

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?

Given the zero-parameter schema and no output schema, the description should clarify the write contract (what gets created/changed/deleted, required state). Instead it focuses on a lock state and contradictory operation claims, leaving the actual write behavior under-specified and inconsistent with annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero parameters, so the baseline is 4. The description mentions environment variables (ABAP_ALLOW_WRITE, ABAP_ALLOW_PACKAGES, ABAP_MODE) that affect behavior, which adds meaning beyond the empty schema, though these are not tool parameters.

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 states a specific verb set (create, change, delete) and resource (ABAP object), and mentions save/check/activate phases. It distinguishes the tool from read-oriented siblings like abap_read or abap_search, though it does not explicitly name alternatives.

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?

It implies usage for writing ABAP objects but provides no explicit when-to-use vs when-not-to-use guidance or comparison to siblings like abap_activate or abap_enh. The lock condition is described, which is a form of conditional availability, but usage context for the write itself is thin.

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