Skip to main content
Glama
Sign In
mcp-dap

mcp-dap

by ztripez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

debug_get_stack_trace

Retrieve the call stack for a thread in an active debug session to see the execution path and pinpoint where the program stopped.

Instructions

Get the call stack for a thread.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session_id": "<session_id>"
    },
    "name": "debug_get_stack_trace"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelsNoNumber of frames to retrieve
thread_idNoThread ID
session_idYesDebug session ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavior. It only states what the tool does, not what it returns, whether it requires a running session, how thread_id defaulting works, or any side effects. This is insufficient for a debug operation.

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, tightly worded sentence with no wasted words. It front-loads the core purpose and is appropriately concise for the tool's simplicity.

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 a straightforward purpose, the description omits essential context: there is no output schema, so return format is unexplained; the meaning of a null thread_id is not addressed; and no guidance is given on when the stack trace is available. An agent would likely need to guess or inspect other tools to use this correctly.

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%, so each parameter already has a description. The tool description adds no additional parameter-specific meaning, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get the call stack for a thread' states a clear verb and resource, making the tool's function immediately understandable. It is distinct enough from siblings like debug_get_threads or debug_get_variables, though it does not explicitly differentiate itself from them.

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?

The description gives no guidance on when to use this tool versus alternatives, no mention of prerequisites (e.g., active debug session), and no exclusions. An agent must infer usage purely from the tool name and sibling list.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools