Skip to main content
Glama
ethanhan2014

SAP ADT MCP Server

by ethanhan2014

unpublish_service_binding

Unpublish an OData service binding from an SAP system by providing the binding name, version, and system ID.

Instructions

Unpublish an OData service binding

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
binding_nameYesService binding name
binding_versionYesService version (e.g. 0001)
system_idNoSAP system ID (e.g. DEV). Omit to use default system.

Implementation Reference

  • Tool registration with input schema for 'unpublish_service_binding'. Defines binding_name and binding_version as required string inputs.
    {
      name: "unpublish_service_binding",
      description: "Unpublish an OData service binding",
      inputSchema: {
        type: "object" as const,
        properties: {
          binding_name: { type: "string", description: "Service binding name" },
          binding_version: { type: "string", description: "Service version (e.g. 0001)" },
          ...SYSTEM_ID_PROP,
        },
        required: ["binding_name", "binding_version"],
      },
    },
  • Handler (switch case) that parses args with ServiceBindingSchema, calls client.unpublishServiceBinding(), and returns the result.
    case "unpublish_service_binding": {
      const { binding_name, binding_version } = ServiceBindingSchema.parse(args);
      const result = await client.unpublishServiceBinding(binding_name, binding_version);
      return { content: [{ type: "text", text: result }] };
    }
  • Actual implementation of unpublishServiceBinding on AdtClient. Sends POST to /sap/bc/adt/ddic/srvb/srvbsources/{name}/unpublish?version={version} with CSRF token.
    async unpublishServiceBinding(name: string, version: string): Promise<string> {
      const encoded = encodeURIComponent(name.toUpperCase());
      return (await this.postWithCsrf(
        `/sap/bc/adt/ddic/srvb/srvbsources/${encoded}/unpublish?version=${encodeURIComponent(version)}`,
        "",
        "*/*"
      )).data as string;
    }
  • ServiceBindingSchema used for both publish and unpublish validation — defines binding_name (string) and binding_version (string) as required fields.
    // Service binding schemas
    const ServiceBindingSchema = z.object({
      binding_name: z.string(),
      binding_version: z.string(),
    });
Behavior2/5

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

No annotations provided; the description simply says 'Unpublish' without disclosing side effects (e.g., whether it destroys the binding, affects running services, or if the action is reversible).

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 sentence, efficient and to the point, though it could be slightly expanded with more context without losing conciseness.

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?

As a mutation tool with no output schema and no annotations, the description lacks information about return values, success/failure indicators, and side effects, leaving the agent under-informed.

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 the parameters; the description adds no extra meaning beyond what is in 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?

The description 'Unpublish an OData service binding' uses a specific verb and resource, clearly distinguishing it from sibling tools like 'publish_service_binding' and 'get_binding_details'.

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?

The description implies usage (to undo a publishing action), but provides no explicit guidance on when to use vs alternatives or any prerequisites like whether the binding must be published.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ethanhan2014/sap-adt-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server