Skip to main content
Glama
ethanhan2014

SAP ADT MCP Server

by ethanhan2014

list_systems

Retrieve a list of all configured SAP systems with their IDs, hostnames, and client numbers to view available connections for development tasks.

Instructions

List all configured SAP systems with their IDs, hostnames, and client numbers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The 'list_systems' tool is registered as part of the tool definitions returned by ListToolsRequestSchema handler. It has no required input parameters and is described as listing all configured SAP systems.
    {
      name: "list_systems",
      description: "List all configured SAP systems with their IDs, hostnames, and client numbers.",
      inputSchema: {
        type: "object" as const,
        properties: {},
        required: [],
      },
    },
  • The handler for 'list_systems' tool call. It calls pool.getSystems(), formats the output as lines showing id: hostname (client, auth) with [default] marker, and returns as text content.
    if (name === "list_systems") {
      const systemList = pool.getSystems()
        .map((s) => `${s.id}: ${s.hostname} (client ${s.client}, auth: ${s.authType})${s.isDefault ? " [default]" : ""}`)
        .join("\n");
      return { content: [{ type: "text", text: systemList }] };
    }
  • The getSystems() method on ClientPool returns an array of system objects (id, hostname, client, authType, isDefault) from the stored systems configuration.
    getSystems(): { id: string; hostname: string; client: string; authType: string; isDefault: boolean }[] {
      return this.systems.map(({ id, hostname, client, authType }) => ({
        id,
        hostname,
        client,
        authType: authType ?? "basic",
        isDefault: id === this.defaultId,
      }));
    }
Behavior3/5

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

With no annotations, the description carries full burden. It correctly indicates a read-only operation returning all configured systems, but does not disclose potential permissions required or performance characteristics.

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?

The description is a single, well-structured sentence that front-loads the action and scope, with no unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list tool, the description is largely complete, stating what it lists and what is returned. It could be enhanced by clarifying if 'all configured' means only systems accessible to the user.

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

Parameters4/5

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

No parameters are present, so the schema coverage is 100%. The description adds value by specifying the return fields (IDs, hostnames, client numbers), which is useful beyond 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 clearly states the verb 'List', the resource 'all configured SAP systems', and specifies what information is returned (IDs, hostnames, client numbers). This differentiates it from sibling list tools like list_system_users, list_traces, etc.

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 explicit guidance on when to use this tool vs alternatives. While it implies listing all systems, it does not mention when not to use it or suggest alternative tools for filtered views.

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