mcp-abap-adt

CreateServiceBinding

Create an OData V2 or V4 service binding (UI or Web API) for a service definition in initial state, with optional activation to expose the service for Fiori or API consumption.

Instructions

Create an OData service binding (V2 or V4, UI or Web API) for a service definition, in initial state. When activate is false, recordable: in batch mode a call is recorded under the next number and answers with empty content; its answer is read by number after the batch ends.

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": {
      "service_binding_name": "<service_binding_name>",
      "service_definition_name": "<service_definition_name>",
      "package_name": "<package_name>"
    },
    "name": "CreateServiceBinding"
  }
}

Input Schema

Name	Required	Description	Default
`detail`	No	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).	terse
`activate`	No	Activate the service binding after create, then read its service group. Default: true.
`description`	No	Optional description. Defaults to service_binding_name when omitted.
`package_name`	Yes	ABAP package name.
`service_name`	No	Published service name. Default: service_binding_name if omitted.
`binding_variant`	No	Service binding variant. ODATA_V4_UI = OData V4 for Fiori Elements, ODATA_V4_WEB_API = OData V4 Web API, ODATA_V2_UI = OData V2 for Fiori Elements, ODATA_V2_WEB_API = OData V2 Web API.	ODATA_V4_UI
`master_language`	No	Optional master/original language for the created object (e.g. "EN", "DE", "ZH"). Defaults to the session language (SAP_LANGUAGE) or EN.
`response_format`	No	Accepted for backward compatibility; no longer affects the answer, which is always the structured write result.	xml
`service_version`	No	Published service version. Default: 0001.
`transport_request`	No	Optional transport request for transport checks.
`service_binding_name`	Yes	Service binding name.
`service_definition_name`	Yes	Referenced service definition name.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv20.1.0Oct 24, 2026

changedInput schema / properties / activate / description

Previous value: -"Activate and generate the service binding after create. Default: true."New value: +"Activate the service binding after create, then read its service group. Default: true."

Changed3 schema fields changedv16.0.0Oct 4, 2026

changedInput schema / properties / activate / description

Previous value: -"Activate service binding after create. Default: true."New value: +"Activate and generate the service binding after create. Default: true."

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"
+}

addedInput schema / properties / response_format / description

Added value: +"Accepted for backward compatibility; no longer affects the answer, which is always the structured write result."

Changed1 schema field changedv8.1.0Jun 26, 2026

addedInput schema / properties / master_language

Added value: +{
+  "description": "Optional master/original language for the created object (e.g. \"EN\", \"DE\", \"ZH\"). Defaults to the session language (SAP_LANGUAGE) or EN.",
+  "type": "string"
+}

Changed3 schema fields changedv6.5.1May 8, 2026

removedInput schema / properties / binding_type

Removed value: -{
-  "default": "ODataV4",
-  "description": "OData binding type.",
-  "enum": [
-    "ODataV2",
-    "ODataV4"
-  ],
-  "type": "string"
-}

addedInput schema / properties / binding_variant

Added value: +{
+  "default": "ODATA_V4_UI",
+  "description": "Service binding variant. ODATA_V4_UI = OData V4 for Fiori Elements, ODATA_V4_WEB_API = OData V4 Web API, ODATA_V2_UI = OData V2 for Fiori Elements, ODATA_V2_WEB_API = OData V2 Web API.",
+  "enum": [
+    "ODATA_V2_UI",
+    "ODATA_V2_WEB_API",
+    "ODATA_V4_UI",
+    "ODATA_V4_WEB_API"
+  ],
+  "type": "string"
+}

removedInput schema / properties / service_binding_version

Removed value: -{
-  "description": "Service binding ADT version. Default inferred from type.",
-  "type": "string"
-}

AddedMar 14, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and delivers real behavioural detail beyond the schema: the object is created in initial (inactive) state, activate=true triggers a post-create read of the service group, and activate=false switches the tool into batch-recording mode where the call returns empty content and must be read back by number. It omits error/permission behaviour and the normal (non-batch) return shape, which keeps it below a 5.

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

Conciseness4/5

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

Two sentences, no filler, with the core purpose and variant scope front-loaded before the conditional behaviour. The second sentence is dense and slightly cryptic ("recordable: in batch mode a call is recorded under the next number"), costing it a point on readability.

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

Completeness3/5

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

For a 12-parameter mutation tool with no annotations and no output schema, the definition covers the creation and activation lifecycle but says nothing about the normal return value, failure modes, or the transport/permission requirements implied by transport_request. Adequate but with clear gaps an agent would discover only by calling it.

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?

Schema description coverage is 100%, so the schema already explains every parameter and the baseline is 3. The description still earns above baseline because it explains the runtime consequence of the activate flag (batch recording, empty answer, read-by-number), which the schema's one-line activate description does not convey.

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?

Names a specific verb and resource ("Create an OData service binding") and narrows the scope by enumerating the four variants (V2/V4, UI/Web API) and the fact that it is created "in initial state". It stops short of naming the sibling it is not — UpdateServiceBinding and ActivateServiceBinding are adjacent operations an agent could confuse it with — so an agent must infer the create-vs-update boundary.

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?

Usage is implied by "in initial state" plus the activate flag, which together tell the agent this is a create-then-optionally-activate step. However, there is no explicit routing guidance against the many neighbouring tools (UpdateServiceBinding, ActivateServiceBinding, CreateServiceDefinition, ListServiceBindingTypes), and no stated prerequisites such as an existing service definition or a transport request.

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

Deploy Server