Skip to main content
Glama

DeleteServiceBinding

Delete an ABAP service binding using the ADT Business Services endpoint. Specify the service binding name and an optional transport request.

Instructions

Delete ABAP service binding via ADT Business Services endpoint.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
service_binding_nameYesService binding name to delete.
transport_requestNoOptional transport request for deletion transport flow.
response_formatNoxml

Implementation Reference

  • The main handler function that deletes an ABAP service binding via ADT Business Services endpoint. Accepts service_binding_name (required), transport_request (optional), and response_format (optional). Calls ADT client to perform the deletion and returns the formatted response.
    export async function handleDeleteServiceBinding(
      context: HandlerContext,
      args: DeleteServiceBindingArgs,
    ) {
      const { connection, logger } = context;
    
      try {
        if (!args?.service_binding_name) {
          throw new Error('service_binding_name is required');
        }
    
        const serviceBindingName = args.service_binding_name.trim().toUpperCase();
        const responseFormat = args.response_format ?? 'xml';
        const client = createAdtClient(connection, logger);
        const state = await client.getServiceBinding().delete({
          bindingName: serviceBindingName,
          transportRequest: args.transport_request,
        });
        const response = state?.deleteResult;
        if (!response) {
          throw new Error(
            `Delete did not return a response for service binding ${serviceBindingName}`,
          );
        }
    
        return return_response({
          data: JSON.stringify(
            {
              success: true,
              service_binding_name: serviceBindingName,
              response_format: responseFormat,
              status: response.status,
              payload: parseServiceBindingPayload(response.data, responseFormat),
            },
            null,
            2,
          ),
          status: response.status,
          statusText: response.statusText,
          headers: response.headers,
          config: response.config,
        });
      } catch (error: any) {
        logger?.error('Error deleting service binding:', error);
        return return_error(error);
      }
    }
  • The TOOL_DEFINITION constant defining the 'DeleteServiceBinding' tool schema including name, description, inputSchema with properties (service_binding_name, transport_request, response_format), and availability for onprem and cloud.
    export const TOOL_DEFINITION = {
      name: 'DeleteServiceBinding',
      available_in: ['onprem', 'cloud'] as const,
      description:
        'Delete ABAP service binding via ADT Business Services endpoint.',
      inputSchema: {
        type: 'object',
        properties: {
          service_binding_name: {
            type: 'string',
            description: 'Service binding name to delete.',
          },
          transport_request: {
            type: 'string',
            description: 'Optional transport request for deletion transport flow.',
          },
          response_format: {
            type: 'string',
            enum: ['xml', 'json', 'plain'],
            default: 'xml',
          },
        },
        required: ['service_binding_name'],
      },
    } as const;
  • Registration of the DeleteServiceBinding tool in the HighLevelHandlersGroup, mapping its toolDefinition (DeleteServiceBinding_Tool) to the handler (withContext(handleDeleteServiceBinding)).
    {
      toolDefinition: DeleteServiceBinding_Tool,
      handler: withContext(handleDeleteServiceBinding),
    },
  • The DeleteServiceBindingArgs TypeScript interface defining the argument types for the handler.
    interface DeleteServiceBindingArgs {
      service_binding_name: string;
      transport_request?: string;
      response_format?: ServiceBindingResponseFormat;
    }
  • Registration of handleDeleteServiceBinding as a compact router handler under SERVICE_BINDING.delete.
    SERVICE_BINDING: {
      create: handleCreateServiceBinding as unknown as CompactHandler,
      get: handleGetServiceBinding as unknown as CompactHandler,
      update: handleUpdateServiceBinding as unknown as CompactHandler,
      delete: handleDeleteServiceBinding as unknown as CompactHandler,
    },
Behavior2/5

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

No annotations provided; the description only states 'Delete' without revealing behavioral traits (e.g., irreversibility, transport requirements, effects on related objects, or return status). A delete operation needs more explicit behavioral disclosure.

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?

Single sentence, no unnecessary words. Efficiently conveys the core action and context.

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 delete tool with no output schema and no annotations, the description is too sparse. It omits critical information like return status, error handling, and prerequisites (e.g., whether the binding must be inactive).

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 67% (two of three parameters have descriptions). The description adds no new parameter context beyond the schema. The missing description for 'response_format' is not compensated.

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 clearly states the action ('Delete') and the resource ('ABAP service binding') with the endpoint context, distinguishing it from sibling delete tools for other entities.

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?

No guidance on when to use this tool versus alternatives (e.g., other delete tools, or when a service binding must be deactivated first). The sibling list includes many similar delete tools, but the description offers no decision context.

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/fr0ster/mcp-abap-adt'

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