Skip to main content
Glama
ethanhan2014

SAP ADT MCP Server

by ethanhan2014

list_system_users

List SAP system users to check transport ownership and perform user lookups. Specify a system ID or use the default system.

Instructions

List SAP system users. Useful for transport ownership and user lookups.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
system_idNoSAP system ID (e.g. DEV). Omit to use default system.

Implementation Reference

  • Handler for the list_system_users tool. Parses no input args (only optional system_id), calls client.getSystemUsers(), and returns the raw response text.
    case "list_system_users": {
      const result = await client.getSystemUsers();
      return { content: [{ type: "text", text: result }] };
    }
  • Helper method in AdtClient that performs an HTTP GET to /sap/bc/adt/system/users to list SAP system users. Returns the raw XML response from the SAP ADT API.
    async getSystemUsers(): Promise<string> {
      const response = await this.http.get<string>(
        "/sap/bc/adt/system/users",
        { headers: { Accept: "*/*" }, responseType: "text" }
      );
      return response.data;
    }
  • Registration of list_system_users tool in the ListToolsRequestSchema handler. Defines no required inputs beyond optional system_id.
      name: "list_system_users",
      description: "List SAP system users. Useful for transport ownership and user lookups.",
      inputSchema: {
        type: "object" as const,
        properties: { ...SYSTEM_ID_PROP },
        required: [],
      },
    },
  • Shared schema constant SYSTEM_ID_PROP used by list_system_users input schema to allow an optional system_id parameter.
    const SYSTEM_ID_PROP = {
      system_id: { type: "string", description: "SAP system ID (e.g. DEV). Omit to use default system." },
    } as const;
Behavior2/5

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

No annotations provided, so the description must disclose behavioral traits. It only states listing users, but does not indicate if it is read-only, permissions needed, or any side effects. Minimal behavioral information.

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?

Two short sentences, no waste. First sentence states purpose, second gives use case. Efficient and front-loaded.

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 with one optional parameter and no output schema, the description is adequate. It covers purpose and usage context. Could mention return format or pagination but not critical.

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 100% with system_id described as optional. Description adds nothing beyond the schema, so baseline 3 is appropriate.

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?

Clearly states the verb 'list' and resource 'SAP system users'. The use case for transport ownership and user lookups differentiates it from sibling tools like list_systems or list_user_transports.

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

Usage Guidelines4/5

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

Explicitly says it is useful for transport ownership and user lookups, implying when to use it. Does not provide when-not-to-use or alternatives, but the context is clear.

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