Skip to main content
Glama

browser_check

Read-onlyIdempotent

Set a checkbox or radio button to checked (default) or unchecked (checked=false) and verify it. ref is an aria-ref or CSS selector; frame = CSS selector of the it is in.

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": {
      "page_id": "<page_id>",
      "ref": "<ref>"
    },
    "name": "browser_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYes
frameNo
checkedNo
page_idYes
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior2/5

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

The description discloses that the tool both mutates state (sets checked/unchecked) and verifies it afterward, which is useful beyond the schema. However, annotations declare readOnlyHint=true while the description explicitly describes changing a control's state, so an agent trusting the annotation would misjudge the side effect. The other hints (idempotentHint=true, destructiveHint=false) are consistent with the described behavior.

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?

Two sentences, both front-loaded with the operative information: what it does and verifies first, parameter semantics second. No redundant restatement of the title and no filler.

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

Completeness3/5

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

For a 5-parameter tool with no output schema and low schema coverage, the description covers the tricky parameters but leaves the required page_id and the in_workspace override unexplained, and it does not say what the verification returns. Adequate but with visible gaps.

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 coverage is only 20%, so the description must compensate, and it largely does: it defines ref as an aria-ref or CSS selector, explains the checked default and the checked=false escape hatch, and identifies frame as the CSS selector of the containing iframe. page_id and in_workspace remain undefined in both schema and description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: set a checkbox or radio button to checked/unchecked and verify the result. The element-type restriction implicitly separates it from browser_click and browser_fill, but it never names a sibling or states that other element types belong elsewhere.

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 is implied by the element types named (checkbox/radio), so an agent can infer this is the right tool for toggling those controls. There is no explicit when-not guidance, no mention of using browser_click for other element types, and no prerequisites such as the element being in view or the page being navigated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.