Mcp-DOM

Overview Schema Source Related Servers Discussions Admin

stop_element_observation

Stop observing a DOM element and compile mutations, diagnostics, network activity, and root-cause analysis into one correlation bundle for debugging UI disappearance or layout changes.

Instructions

Stop focused element observation and assemble a complete correlation bundle with mutations, diagnostics, network activity, and root-cause analysis.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Sep 1, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations present, the description carries the full burden and does provide meaningful behavior beyond the name: it will stop observation and generate a bundle containing mutations, diagnostics, network activity, and root-cause analysis. It does not however disclose side effects, whether existing observation sessions are terminated globally, or any irreversible effects.

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?

A single, front-loaded sentence states the action first and then the output. Every part adds information, with no redundancy or 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-parameter tool, the description covers both the action and the content of the returned bundle, which is especially important given there is no output schema. It could be slightly more complete by explicitly linking to start_element_observation, but the sibling list and the wording make that connection clear.

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?

The tool has zero parameters, so there are no parameter semantics to explain. The description focuses instead on behavior and output, which is appropriate and leaves no parameter-related gaps.

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 names a specific action and resource: 'Stop focused element observation' and then specifies the expected output ('assemble a complete correlation bundle...'). It is clearly distinguishable from sibling tools like stop_element_picker and is the natural counterpart to start_element_observation.

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

Usage Guidelines3/5

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

The description implicitly signals that this tool is used to end a focused element observation and produce a summary bundle. However, it does not explicitly state when to use it versus alternatives such as stop_element_picker or inspect_live_element, nor mention prerequisites like a prior start_element_observation call.

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