Skip to main content
Glama
Sign In
PhantomHand

PhantomHand

by SilenceEchoLab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

browser_check

Check or uncheck a checkbox or radio button on a web page using a CSS selector. Enables programmatic control of form elements via browser automation.

Instructions

Check or uncheck a checkbox or radio button by CSS selector.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "selector": "<selector>",
      "checked": "<checked>"
    },
    "name": "browser_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
checkedYes
selectorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.1/5.0
Behavior2/5

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

The description only states the basic action but lacks details about prerequisites (element must exist, be interactive), side effects (does it trigger events?), or limitations (what if element is disabled?). With no annotations, this level of transparency is insufficient.

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

Conciseness4/5

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

The description is a single clear sentence with no unnecessary words. It is concise and front-loaded, but could be slightly improved by adding a brief usage note without becoming verbose.

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

Completeness2/5

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

For a tool with two required parameters and no output schema, the description is minimal. It lacks information about expected behavior when the element is not found, whether the tool returns anything, or any constraints on the selector. In the context of many sibling tools, it does not fully equip an AI agent to use it correctly.

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?

The description adds context to the 'selector' parameter by specifying it's a CSS selector, and implies the 'checked' boolean toggles the state. However, it does not clarify the exact meaning of true/false or provide examples. Given 0% schema coverage, it adds some value but not enough to fully compensate.

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 it checks/unchecks a checkbox or radio button using a CSS selector, which distinguishes it from sibling tools like browser_click or browser_set_value that are for generic clicks or text input.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. It does not mention any contexts where it should or should not be used, nor does it reference sibling tools.

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