Skip to main content
Glama
Sign In
Mcp-DOM

Mcp-DOM

by IrMaho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

stop_element_picker

Deactivate the visual element picker mode and restore normal cursor and interaction state in the browser. Use this action when you need to exit picker mode and regain control of the page.

Instructions

Deactivate the visual element picker mode in the browser and restore normal cursor and interaction state.

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_picker"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations present, the description carries the behavioral disclosure burden. It clearly states the effect: deactivating picker mode and restoring normal cursor/interaction state. It does not mention edge cases such as idempotency or behavior when no picker is active, but for a simple state-toggle tool the disclosed behavior is sufficient.

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, well-structured sentence that front-loads the action and clearly states the outcome. Every word earns its place with no redundancy or filler.

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?

For a parameterless tool with no output schema, the description is complete. It explains what the tool does and what state change occurs, and sibling tools provide sufficient surrounding context. Nothing essential is missing.

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 the schema is trivially complete. The baseline for zero-parameter tools is 4, and the description adds no unnecessary parameter information, which is appropriate.

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?

Description uses a specific verb (Deactivate) with a clear resource (visual element picker mode) and states the resulting state change (restore normal cursor and interaction state). It clearly differentiates itself from siblings like start_element_picker by being the inverse operation.

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?

Usage context is implied: the tool should be used when the visual element picker mode is active and needs to be turned off, especially after calling start_element_picker. However, no explicit when-to-use or alternative routing is provided, so the guidance is inferred rather than stated.

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