Skip to main content
Glama
ethanhan2014

SAP ADT MCP Server

by ethanhan2014

get_debugger_session

Check if a debugger session is attached to an SAP system. Returns session information without blocking, using optional terminal, IDE, user, and system identifiers.

Instructions

Check if a debugger session is currently attached. Returns session info without blocking.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
terminal_idNoTerminal identifier (default: MCP_TERMINAL)
ide_idNoIDE identifier (default: MCP_IDE)
userNoSAP username (default: current user)
system_idNoSAP system ID (e.g. DEV). Omit to use default system.

Implementation Reference

  • Handler for 'get_debugger_session' tool: parses input with DebuggerSessionSchema, calls client.debuggerGetSession(), returns the result.
    case "get_debugger_session": {
      const { terminal_id, ide_id, user } = DebuggerSessionSchema.parse(args);
      const result = await client.debuggerGetSession(terminal_id, ide_id, user);
      return { content: [{ type: "text", text: result }] };
    }
  • Tool registration for 'get_debugger_session' including description and input schema definition.
    {
      name: "get_debugger_session",
      description: "Check if a debugger session is currently attached. Returns session info without blocking.",
      inputSchema: {
        type: "object" as const,
        properties: {
          terminal_id: { type: "string", description: "Terminal identifier (default: MCP_TERMINAL)" },
          ide_id: { type: "string", description: "IDE identifier (default: MCP_IDE)" },
          user: { type: "string", description: "SAP username (default: current user)" },
          ...SYSTEM_ID_PROP,
        },
        required: [],
      },
    },
  • Input schema (DebuggerSessionSchema) for get_debugger_session: terminal_id, ide_id, user (all optional).
    const DebuggerSessionSchema = z.object({
      terminal_id: z.string().optional(),
      ide_id: z.string().optional(),
      user: z.string().optional(),
    });
  • AdtClient.debuggerGetSession() — the actual HTTP implementation: calls GET /sap/bc/adt/debugger/listeners to check session status without blocking.
    async debuggerGetSession(terminalId = "MCP_TERMINAL", ideId = "MCP_IDE", user?: string): Promise<string> {
      this.ensureDebugSession();
      const u = encodeURIComponent((user ?? this.config.username).toUpperCase());
      const resp = await this.http.get(
        `/sap/bc/adt/debugger/listeners?debuggingMode=user&terminalId=${encodeURIComponent(terminalId)}&ideId=${encodeURIComponent(ideId)}&requestUser=${u}`,
        {
          headers: this.statefulHeaders({ Accept: "application/xml" }),
          responseType: "text",
        }
      );
      return resp.data as string;
    }
Behavior3/5

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

The description mentions 'without blocking', a useful behavioral trait. However, it does not disclose authentication requirements, whether session info includes errors or empty states, or any side effects. No annotations are provided to supplement.

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 sentences, front-loaded with purpose, no wasted words. Every sentence adds value, and the structure is clear and direct.

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

Completeness3/5

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

The tool has no output schema, and the description only vaguely mentions 'Returns session info'. It does not detail what fields are included or possible statuses. Given the complexity of debugger state, a more complete description would be beneficial.

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?

All four parameters are covered in the input schema with descriptions. The tool description adds no additional semantics beyond the schema. With 100% schema coverage, baseline score of 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?

The description uses a specific verb 'Check' and resource 'debugger session', clearly indicating a read-only operation. It distinguishes from sibling tools like attach_debugger, start_debugger_listener, and debugger_step that perform actions or mutations.

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 when needing to check session status without blocking, but gives no explicit guidance on when to use this tool vs alternatives such as get_debugger_stack or get_debugger_variables. No when-not conditions are stated.

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