Skip to main content
Glama
fr0ster

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

CreateServiceBinding

Creates an OData service binding (V2 or V4, UI or Web API) from a service definition in initial state, optionally activating and generating it.

Instructions

Create an OData service binding (V2 or V4, UI or Web API) for a service definition, in initial state.

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 and generate the service binding after create. Default: true.
descriptionNoOptional description. Defaults to service_binding_name when omitted.
package_nameYesABAP package name.
service_nameNoPublished service name. Default: service_binding_name if omitted.
binding_variantNoService 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_languageNoOptional master/original language for the created object (e.g. "EN", "DE", "ZH"). Defaults to the session language (SAP_LANGUAGE) or EN.
response_formatNoAccepted for backward compatibility; no longer affects the answer, which is always the structured write result.xml
service_versionNoPublished service version. Default: 0001.
transport_requestNoOptional transport request for transport checks.
service_binding_nameYesService binding name.
service_definition_nameYesReferenced service definition name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv16.0.0
    • 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."
  2. Changed1 schema field changedv8.1.0
    • 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"
+}
  3. Changed3 schema fields changedv6.5.1
    • 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"
-}
  4. Added

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose that the binding is created "in initial state" (inactive), which is useful, but it omits transport/permission prerequisites, what happens on failure, and how the default activate=true interacts with that initial state.

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?

A single front-loaded sentence with no filler. For a 12-parameter mutation tool it is arguably too terse, which keeps it from a 5, but every word earns its place.

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?

For a 12-parameter write tool with no annotations and no output schema, the description is thin. It says nothing about which parameters are required, transport handling, activation semantics, or error behavior, so an agent lacks the context needed to invoke it confidently.

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 all 12 parameters are already documented in the schema. The description's variant naming (V2 or V4, UI or Web API) merely restates the binding_variant enum rather than adding new meaning. Baseline 3 applies.

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?

States a specific verb (Create) and resource (OData service binding), and scopes it to a service definition with the V2/V4 and UI/Web API variants named. It is distinguishable from UpdateServiceBinding/DeleteServiceBinding by the verb, though it never explicitly names those siblings.

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?

"in initial state" implies the object is created inactive and may need ActivateServiceBinding, but the description never states when to use this versus ActivateServiceBinding or ValidateServiceBinding. Usage is only implied, not spelled out.

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