Skip to main content
Glama

resume

Resumes a page paused in the debugger at a breakpoint, step, or exception. Returns the paused state and location, or null if execution continued.

Instructions

Resumes a page paused in the debugger (a breakpoint, a step, an exception or its own debugger statement). Returns {paused, location: {url, line_number, column_number} | null} (0-based): paused only if it stopped again within 250 ms (another breakpoint).

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": "resume"
  }
}

Input Schema

NameRequiredDescriptionDefault
tab_idNoDefault: the active tab.
instance_idNoDefault: 'default'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-rc.1

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does well: it documents the return shape, that location is 0-based and null when not paused again, and the non-obvious 250 ms window that governs the paused flag. It omits whether a debugger attachment/session is required and what error surfaces if the tab is not paused.

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?

Two sentences, front-loaded with the action, and every clause carries information the agent cannot get elsewhere — cause enumeration, return shape, index base, and timing semantics. No filler.

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

Completeness4/5

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

For a zero-required-parameter tool with no output schema, the description supplies the return value contract itself, which is exactly what is needed. Only the failure/precondition behavior for a non-paused page is left unstated.

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% and both parameters (tab_id, instance_id) already carry default descriptions in the schema. The description adds no interpretation of these parameters, so the baseline 3 applies.

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?

States a specific verb ("Resumes") and a precisely scoped resource ("a page paused in the debugger"), then enumerates the pause causes it clears: breakpoint, step, exception, or the page's own debugger statement. An agent can tell exactly what state this tool transitions out of, which no sibling in the catalog does.

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 condition for use is clear: the page must be paused in the debugger, and the parenthetical lists the qualifying pause types. It does not state what happens when called on a non-paused page or name an explicit alternative, so it falls short of full when/when-not routing.

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