Skip to main content
Glama
Yan-Vi

easy-spec-mcp

by Yan-Vi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

live_detach

End the live debugging session on the current tab, releasing the Chrome debugger attachment to remove the 'being debugged' banner and free resources after exploration.

Instructions

Detaches chrome.debugger from the side panel's target tab right away, instead of waiting out the ~20s idle timeout every other live_* call leaves it attached for (see live_snapshot/ live_run_step/live_pick_element -- they keep the tab attached across a quick back-and-forth burst of calls rather than detaching after each individual one, since detaching mid-exploration was closing transient page UI like an open dropdown). Call this when done with a live exploration/interaction sequence, so Chrome's "being debugged" banner does not linger on the tab longer than necessary.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectNoPath to the project root (same folder the side panel connects to). Defaults to the EASYSPEC_PROJECT environment variable if omitted.
sessionNoWhich connected side panel to target, by its connection id (see live_status) -- only needed when more than one side panel is connected to the same project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.4

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It explains the immediate-detach behavior versus the idle timeout, and mentions the side effect on the banner. It does not cover potential failure modes or idempotency, but for a simple detach action it is fairly transparent.

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

Conciseness3/5

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

The description is front-loaded with the main action but becomes verbose and somewhat repetitive, especially in the first sentence with the long parenthetical about other live_* tools. It could be trimmed without losing information.

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 simple detach action with no output schema, the description provides sufficient context: when to use, why, and the trade-off compared to other tools. It does not mention reconnect behavior, but that is not necessary for the core action.

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% and both parameters have clear descriptions. The tool description itself does not add extra semantic detail about the parameters beyond what is in the schema, so it stays at the baseline for high coverage.

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 clearly states the tool's action (detaches chrome.debugger immediately) and distinguishes it from other live_* tools that keep the tab attached. It names the specific alternative behavior and the reason for it.

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 instructs when to call the tool ('Call this when done with a live exploration/interaction sequence') and provides a concrete motivation (avoid lingering 'being debugged' banner). It also implicitly indicates when not to use it (when continued interaction is needed).

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