Skip to main content
Glama
Sign In
python-dap-mcp

python-dap-mcp

by MikeWinkelmannXL2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

end_session

Terminate the current debugging session and stop the debuggee process, freeing resources after script inspection.

Instructions

End the active debug session and terminate the debuggee.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "end_session"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

The description explicitly discloses the side effect of terminating the debuggee, which is not captured in the annotations. This is valuable behavioral information beyond the structured metadata. There is no contradiction with the annotations since neither openWorldHint nor destructiveHint directly conflicts with ending a debug session.

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 sentence with a front-loaded verb and no filler or redundant detail. Every word earns its place, making it optimally concise.

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

Completeness5/5

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

For a parameterless tool with an output schema present, the description fully defines the tool's purpose and the primary side effect (terminating the debuggee). No further elaboration is needed.

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?

The input schema has zero parameters, so the description correctly avoids parameter explanation. With no parameters to document, the baseline of 4 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 the specific verb 'End' with the resource 'active debug session' and further clarifies 'terminate the debuggee'. This unambiguously states what the tool does and distinguishes it from sibling tools that focus on breakpoints, stepping, or continuation.

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?

The phrase 'active debug session' implies this tool should be used when a session is running and needs to be stopped. No sibling tool provides an alternative termination mechanism, so the context is clear, though explicit exclusions or alternative guidance are not provided.

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