Skip to main content
Glama
fr0ster

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

UpdateServiceBinding

Change the publication state of an existing ABAP service binding to published or unpublished, controlling OData service exposure in SAP systems.

Instructions

Update publication state of an existing ABAP service binding.

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
service_nameYesPublished service name, from the binding. Required: an OData V2 publication job resolves the service by name and version and refuses without them. Ignored for V4, where the request names its target on its own.
binding_variantNoService binding variant. Determines OData version for publish/unpublish routing.ODATA_V4_UI
response_formatNoAccepted for backward compatibility; no longer affects the answer, which is always the structured write result.xml
service_versionNoPublished service version. Default 0001. Used by an OData V2 publication job together with the service name; ignored for V4.
service_binding_nameYesService binding name to update.
desired_publication_stateYesTarget publication state.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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"
+}
    • addedInput schema / properties / response_format / description
      Added value: +"Accepted for backward compatibility; no longer affects the answer, which is always the structured write result."
    • changedInput schema / properties / service_name / description
      Previous value: -"Published service name."New value: +"Published service name, from the binding. Required: an OData V2 publication job resolves the service by name and version and refuses without them. Ignored for V4, where the request names its target on its own."
    • changedInput schema / properties / service_version / description
      Previous value: -"Published service version. Optional."New value: +"Published service version. Default 0001. Used by an OData V2 publication job together with the service name; ignored for V4."
  2. Changed2 schema fields changedv6.5.1
    • addedInput schema / properties / binding_variant
      Added value: +{
+  "default": "ODATA_V4_UI",
+  "description": "Service binding variant. Determines OData version for publish/unpublish routing.",
+  "enum": [
+    "ODATA_V2_UI",
+    "ODATA_V2_WEB_API",
+    "ODATA_V4_UI",
+    "ODATA_V4_WEB_API"
+  ],
+  "type": "string"
+}
    • removedInput schema / properties / service_type
      Removed value: -{
-  "default": "ODataV4",
-  "description": "OData service type for publish/unpublish action routing.",
-  "enum": [
-    "ODataV2",
-    "ODataV4"
-  ],
-  "type": "string"
-}
  3. Added

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It states the operation is an update, but does not describe permissions, side effects, reversibility, prerequisites, or what the response contains.

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?

The description is a single front-loaded sentence with no filler. It is concise, though its brevity contributes to a lack of operational detail.

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 mutation tool with seven parameters, no annotations, and no output schema, a single sentence is insufficient. The description should at least note that this is a write operation with side effects and what inputs are required, even if the schema carries most parameter detail.

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 all seven parameters in detail. The description only echoes the concept of 'publication state' and adds no parameter-specific meaning beyond that baseline.

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 and resource: 'Update publication state of an existing ABAP service binding.' This clearly separates the tool from read, create, delete, and activate siblings, though it does not explicitly name any alternative.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives such as ActivateServiceBinding, ValidateServiceBinding, or CreateServiceBinding. The only usage signal is the implied need to change publication state.

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