Skip to main content
Glama

browser_set_checked

browser_set_checked
Idempotent

Sets a checkbox or radio button to a specific checked state in a browser tab, so agents can toggle form options reliably by element ID.

Instructions

Set a checkbox or radio button to a specific checked state.

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": {
      "tab_id": "<tab_id>",
      "element_id": "<element_id>",
      "checked": "<checked>"
    },
    "name": "browser_set_checked"
  }
}

Input Schema

NameRequiredDescriptionDefault
tab_idYes
checkedYes
frame_idNoChrome frame ID inside the tab from browser_get_frames. 0 is the top document, which is the default.
element_idYesOpaque element_id returned by browser_get_interactives.
session_idNoSession that owns the tab. Pass it on every call so the runtime can refuse a tab another session holds.
session_nameNoName for this conversation's Chrome tab group, so the tab bar reads as the task instead of a generated id. Sticky: pass it once when the name becomes clear, and again only to rename.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety and idempotency profile is covered. The description's only added nuance is that it sets an explicit state rather than toggling, which is essentially already implied by idempotentHint; it says nothing about failures on wrong element types, frames, or session ownership.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity borders on under-specification rather than tightness.

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 six-parameter mutation tool with no output schema and only partial schema descriptions, the definition leaves key operational details unstated: where element_id comes from, how frame_id interacts with the element, and the session ownership requirement. The schema covers some of this, but the description does not compensate for the gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 67%, with tab_id and checked undocumented in the schema, and the description adds no parameter meaning at all beyond the word 'checked'. It does not explain element_id provenance, frame_id selection, or the session_id/session_name contract.

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?

The description states a specific verb and resource: it sets a checkbox or radio button to a given checked state. That is clear enough to act on, but it does not distinguish the tool from siblings like browser_click, which can also change a checkbox's state.

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?

There is no guidance on when to use this tool versus browser_click or browser_select_option, and no stated preconditions such as needing an element_id from browser_get_interactives. The agent must infer the usage context entirely.

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