Skip to main content
Glama

ListServiceBindingTypes

Retrieve available service binding types (ODataV2, ODataV4) from the ADT Business Services endpoint.

Instructions

List available service binding types (for example ODataV2/ODataV4) from ADT Business Services endpoint.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
response_formatNoxml

Implementation Reference

  • Main handler function that executes the 'ListServiceBindingTypes' tool logic. Creates an ADT client, calls getServiceBindingTypes(), and returns parsed response.
    export async function handleListServiceBindingTypes(
      context: HandlerContext,
      args: ListServiceBindingTypesArgs = {},
    ) {
      const { connection, logger } = context;
    
      try {
        const responseFormat = args.response_format ?? 'xml';
        const client = createAdtClient(connection, logger);
        const response = await client.getServiceBinding().getServiceBindingTypes();
    
        return return_response({
          data: JSON.stringify(
            {
              success: true,
              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 listing service binding types:', error);
        return return_error(error);
      }
    }
  • Tool definition including name 'ListServiceBindingTypes', availability, description, and input schema with optional response_format parameter (xml/json/plain).
    export const TOOL_DEFINITION = {
      name: 'ListServiceBindingTypes',
      available_in: ['onprem', 'cloud'] as const,
      description:
        'List available service binding types (for example ODataV2/ODataV4) from ADT Business Services endpoint.',
      inputSchema: {
        type: 'object',
        properties: {
          response_format: {
            type: 'string',
            enum: ['xml', 'json', 'plain'],
            default: 'xml',
          },
        },
      },
    } as const;
  • TypeScript interface for the handler arguments, accepting optional response_format.
    interface ListServiceBindingTypesArgs {
      response_format?: ServiceBindingResponseFormat;
    }
  • Import of the tool definition (aliased as ListServiceBindingTypes_Tool) and handler function into the HighLevelHandlersGroup.
    import {
      handleListServiceBindingTypes,
      TOOL_DEFINITION as ListServiceBindingTypes_Tool,
    } from '../../../handlers/service_binding/high/handleListServiceBindingTypes';
  • Registration of the tool in the high-level handlers group, mapping ListServiceBindingTypes_Tool to handleListServiceBindingTypes with context.
    {
      toolDefinition: ListServiceBindingTypes_Tool,
      handler: withContext(handleListServiceBindingTypes),
    },
Behavior3/5

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

No annotations are provided, so the description must carry the burden. It mentions the source endpoint but does not disclose read-only nature, side effects, or output format. The description is basic but not misleading.

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 redundant verbiage. Efficiently conveys the core purpose.

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?

Despite low complexity (1 optional param, no output schema), the description omits parameter details and return value explanation. It is insufficient for an agent to properly invoke the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, and the description adds no information about the lone parameter 'response_format'. The parameter has enum values and a default, but the agent receives no guidance on how to use it.

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 tool lists service binding types with examples (ODataV2/ODataV4), distinguishing it from sibling tools that create, update, or delete specific objects. It has a specific verb and resource.

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 for listing binding types but provides no explicit context on when to use it vs alternatives, nor any exclusions. The sibling list is diverse, but usage guidance is implicit.

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