abap-config-mcp

Poll Async Customizing Write

customizing_status

Read-onlyIdempotent

Poll an asynchronous customizing write by run_id until it reports ok or error, so you can confirm background commit and transport-recording results after a pending apply.

Instructions

Check the result of an asynchronous customizing write (customizing_apply with commit: true) by its run_id. The write runs in a background job for headless transport recording; if it doesn't finish within apply's poll budget, apply returns a run_id — use this tool to poll until it reports ok/error.

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": {
      "runId": "<runId>"
    },
    "name": "customizing_status"
  }
}

Input Schema

Name	Required	Description
`runId`	Yes	The run_id returned by a pending customizing_apply commit
`icfPath`	No	SICF path of the engine (default: /sap/bc/zmcp_cust)
`connectionId`	No	SAP system connection ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.16.0Nov 12, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so safety is covered; the description adds the crucial context that the actual write executes in a background job for headless transport recording, which explains why a read-only poll tool exists for a write. It does not add detail on polling cadence, terminal state payloads, or what happens if the background job never completes, which keeps it below 5.

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?

Two sentences, front-loaded with what the tool does and why, then the precise condition for invoking it. No redundant restatement of the title or schema.

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 simple single-required-parameter polling tool with full schema coverage and no output schema, the description explains the lifecycle link to customizing_apply well enough to call it correctly. Minor gap: no guidance on terminal/non-terminal status values or polling interval, though 'ok/error' is named.

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% and each parameter carries its own description, so the baseline is 3. The description reinforces that runId comes from a pending customizing_apply commit but adds no extra meaning for icfPath or connectionId beyond the schema.

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?

States a specific verb (check/poll), a specific resource (the result of an asynchronous customizing write), and keys it to the runId returned by customizing_apply with commit:true. It explicitly positions itself relative to the sibling customizing_apply, so an agent can tell it apart.

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

Usage Guidelines5/5

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

Gives the exact trigger condition: apply's poll budget expired and apply returned a run_id, then use this tool to poll until ok/error. The when-to-use and the terminating condition are both explicit, and the alternative (apply itself) is named.

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

Deploy Server