Skip to main content
Glama
SLP-DEV1

qwen-dap-mcp

by SLP-DEV1
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

Continue Execution

debug_continue
Destructive

Resume a paused debugger thread to continue execution until the next stop or exit. Use after inspecting a halted state; not for crash dumps, as postmortem targets cannot resume.

Instructions

Resume one paused thread in a live debug session. Use this after inspecting a stopped state when execution should proceed to the next stop or termination; do not use it for crash dumps because postmortem targets cannot resume. This changes debuggee execution state and may allow the target to perform normal application side effects before the next stop.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
threadIdYesDAP thread identifier to resume; obtain it from debug_snapshot, debug_status, or a stopped event.
sessionIdNoOptional DAP session ID. Omit to use the backward-compatible default session.
timeoutMsNoMaximum time in milliseconds to wait for the next stopped event when waitForStop is true.
waitForStopNoWhen true, wait for the next stopped event before returning; when false, return after the continue request is accepted.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
stoppedNo
responseNo
allThreadsContinuedNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv0.17.0
    • addedInput schema / properties / sessionId
      Added value: +{
+  "description": "Optional DAP session ID. Omit to use the backward-compatible default session.",
+  "maxLength": 64,
+  "minLength": 1,
+  "pattern": "^[A-Za-z0-9][A-Za-z0-9._-]{0,63}$",
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "allThreadsContinued": {
+      "type": "boolean"
+    },
+    "response": {},
+    "stopped": {}
+  },
+  "type": "object"
+}
  2. Changed3 schema fields changedv0.12.1
    • addedInput schema / properties / threadId / description
      Added value: +"DAP thread identifier to resume; obtain it from debug_snapshot, debug_status, or a stopped event."
    • addedInput schema / properties / timeoutMs / description
      Added value: +"Maximum time in milliseconds to wait for the next stopped event when waitForStop is true."
    • addedInput schema / properties / waitForStop / description
      Added value: +"When true, wait for the next stopped event before returning; when false, return after the continue request is accepted."
  3. First observedv0.6.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already mark the tool as destructive and non-read-only, and the description reinforces this by disclosing that continuing can change debuggee execution state and allow normal application side effects before the next stop. This is exactly the kind of behavioral context that annotations alone do not provide.

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?

Three sentences, each with a distinct job: state the action, give usage rules, and warn of side effects. The core purpose is front-loaded and there is no redundant or filler prose.

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?

Given that an output schema exists, return values need no explanation in the description. The description covers the live-session constraint, the postmortem exclusion, and the side-effect risk, leaving only details already present in the schema.

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 description coverage is 100%, so the baseline is 3. The description adds little parameter-specific meaning—it only reinforces that exactly one thread is resumed, while all parameter details already live in the schema.

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 first sentence states a specific verb and resource: resume one paused thread in a live debug session. It also explicitly excludes crash dumps, which distinguishes it from sibling dump-analysis tools without needing to open their schemas.

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 description clearly says when to use it ('after inspecting a stopped state when execution should proceed to the next stop or termination') and when not to use it ('do not use it for crash dumps'). However, it does not name an alternative tool to use for crash dumps, so the routing guidance stops short of a full 5.

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/SLP-DEV1/qwen-dap-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server