Skip to main content
Glama
Sign In
ForgeMCP

ForgeMCP

by hardened-steel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

debugger_continue

Destructive

Resume debugger execution from an expected stop using the session ID and stop token, then wait on the returned execution reference with an optional timeout.

Instructions

Continue from an expected stop; wait using the returned execution reference.

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>",
      "stop": "<stop>"
    },
    "name": "debugger_continue"
  }
}

Input Schema

NameRequiredDescriptionDefault
stopYes
timeoutNo
session_idYes

Output Schema

NameRequiredDescriptionDefault
snapshotYes
executionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.1

TDQS

C2.4/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false and destructiveHint=true, so the agent knows this mutates execution state, but the description adds nothing about that risk (resuming a paused/possibly faulting process, breakpoints re-triggering). 'Wait using the returned execution reference' is vague and does not clarify blocking behavior or the timeout interaction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the failure is under-specification rather than verbosity, and the second clause is poorly anchored to any actual parameter.

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?

This is a state-mutating debugger operation with three parameters and zero top-level parameter documentation; even with an output schema present, the description does not tell the agent what is required to invoke it safely or what 'continue' implies for a paused session.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Top-level schema coverage is 0%: neither session_id nor timeout has any property-level description, and the description only obliquely alludes to the stop token via 'expected stop'. It says nothing about the timeout parameter's role, optionality, or 300-second cap, and does not explain that the stop token expires on resume (only the nested $defs do).

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

Purpose3/5

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

The verb 'Continue' plus the debugger context conveyed by the name and 'expected stop' gives a rough sense of resuming execution, but 'expected stop' and 'execution reference' are unexplained jargon, and nothing distinguishes this from sibling tools like debugger_step, debugger_wait, or debugger_pause.

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?

There is no explicit guidance on when to use this versus debugger_step or debugger_wait, nor on prerequisites such as needing a stop token from debugger_get. The only hint is the implicit notion of continuing 'from an expected stop'.

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