js-reverse-mcp

by zhangjia2024

Overview Schema Source Related Servers Discussions Admin

pause_or_resume

Pause a running JavaScript execution immediately or resume a paused session after inspection; choose the explicit action instead of relying on implicit toggling.

Instructions

Explicitly requests an immediate pause or resumes an existing paused execution; it never toggles implicitly. Use a code breakpoint or break_on_xhr instead when a specific statement/request should stop, and use get_paused_info before resuming if evidence must be collected. Resuming invalidates current callFrameIds and frame indices.

Input Schema

Name	Required	Description	Default
`action`	Yes	Use "pause" only while running, or "resume" only after a breakpoint/manual pause. Resume after get_paused_info/evaluate_script/step inspection is complete.

Output Schema

Name	Required	Description
`ok`	Yes	Whether the tool completed successfully.
`data`	No	Machine-readable result payload.
`tool`	Yes	Stable MCP tool name.
`error`	No
`summary`	Yes	Concise human-readable outcome.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv4.0.5Oct 25, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Discloses state-changing behavior and invalidation side effect. While annotations are limited, description adds useful context beyond them. Could be improved by noting error scenarios.

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?

Concise, front-loaded with main purpose, then alternatives and side effects. No redundant sentences.

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?

Complete for a simple tool: single parameter fully described, usage prerequisites, side effect noted. Given schema coverage and output schema presence, further detail unnecessary.

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?

Schema covers enum with descriptions; description adds valuable usage tips (when to use each value, ordering) that go beyond 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?

Clearly states it pauses or resumes execution explicitly, never toggles. Contrasts with break_on_xhr and step, providing clear purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly describes when to use alternatives (break_on_xhr, get_paused_info) and warns that resuming invalidates callFrameId, offering clear guidance.

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