Skip to main content
Glama
ethanhan2014

SAP ADT MCP Server

by ethanhan2014

get_debugger_stack

Retrieve the current call stack from the SAP debugger to analyze program execution flow and identify the context of active procedures.

Instructions

Get the current call stack in the debugger

Input Schema

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

Implementation Reference

  • The AdtClient.debuggerGetStack() method is the core handler. It makes a POST request to /sap/bc/adt/debugger?method=getStack with stateful headers to retrieve the current debugger call stack. Returns raw XML response from the SAP ADT debugger API.
    async debuggerGetStack(): Promise<string> {
      this.ensureDebugSession();
      const resp = await this.http.post(
        "/sap/bc/adt/debugger?method=getStack",
        "",
        {
          headers: this.statefulHeaders({ Accept: "application/xml" }),
          responseType: "text",
        }
      );
      return resp.data as string;
    }
  • The input schema for get_debugger_stack defines it accepts only the optional system_id parameter (via SYSTEM_ID_PROP), with no required properties.
      name: "get_debugger_stack",
      description: "Get the current call stack in the debugger",
      inputSchema: {
        type: "object" as const,
        properties: { ...SYSTEM_ID_PROP },
        required: [],
      },
    },
  • The tool is registered in the MCP server's ListToolsRequestSchema handler with name 'get_debugger_stack' and description 'Get the current call stack in the debugger'.
    {
      name: "get_debugger_stack",
      description: "Get the current call stack in the debugger",
      inputSchema: {
        type: "object" as const,
        properties: { ...SYSTEM_ID_PROP },
        required: [],
      },
    },
  • The MCP server's CallToolRequestSchema handler dispatches 'get_debugger_stack' to client.debuggerGetStack() and returns the text result.
    case "get_debugger_stack": {
      const result = await client.debuggerGetStack();
      return { content: [{ type: "text", text: result }] };
    }
Behavior2/5

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

With no annotations, the description should disclose behavior. It only states 'get', implying a read operation, but does not mention dependencies (e.g., requires an active debugger session via attach_debugger) or side effects.

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 concise sentence that front-loads the verb and resource, with no unnecessary words.

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?

Given the optional parameter and lack of output schema, the description should specify prerequisites (e.g., active debug session) and what the result contains (e.g., stack frames). It does not, leaving gaps.

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 one optional parameter system_id already described in the schema. The description adds no additional meaning beyond what the schema provides, 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?

The description clearly states the action 'Get' and the resource 'the current call stack in the debugger', distinguishing it from sibling tools like debugger_goto_stack (navigation) and get_debugger_variables (variables).

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 is provided on when to use this tool versus alternatives (e.g., debugger_goto_stack to navigate the stack). The description lacks context about prerequisites such as an active debugger session.

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