Skip to main content
Glama
Sign In
vibatchium

vibatchium

by trueoriginlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

uncheck

Deselect a checkbox to clear its checked state in the browser.

Instructions

Uncheck a checkbox.

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": {
      "target": "<target>"
    },
    "name": "uncheck"
  }
}

Input Schema

NameRequiredDescriptionDefault
leaseNoOptional lease token to present if the target session is leased (0.7.0). Threaded per-call; never read from the server's env.
targetYes@eN or selector.
sessionNoOptional session name to target (omit for the shared 'default'). On a daemon shared with other agents, pass a UNIQUE name for stateful multi-step work (go→click→fill) so you don't collide on 'default'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states only 'uncheck a checkbox' with no indication of idempotency, error behavior for non-checkbox elements, or side effects. This is a significant gap for a mutating action, leaving the agent without expectations about state changes or failure modes.

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?

The description is a single, clear sentence with no superfluous words. It is front-loaded with the exact action and object, achieving maximum clarity per word. This is an example of effective conciseness, not under-specification.

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?

The tool is simple, and the schema covers parameters fully. However, there is no output schema and no behavioral detail about the action's effects or prerequisites. For a mutating action on UI elements, an agent would benefit from knowing idempotency or typical use cases. The description is adequate for a simple action but leaves some gap regarding expected outcomes.

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 input schema provides full coverage (100%) with descriptions for all parameters: target, lease, and session. The description itself adds nothing beyond the schema. Since the schema already documents each parameter, a baseline of 3 is appropriate; the description does not enhance the semantics.

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 clearly states the verb 'uncheck' and the resource 'a checkbox', making the core action unambiguous. It distinguishes itself from the sibling 'check' by inversion, though it does not explicitly name the sibling or explain the difference. The name itself conveys the inverse operation, so an agent can infer the purpose.

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 alternatives like 'check' or 'click'. No mention of preconditions, such as whether the element must already be checked, or scenarios where this is appropriate. An agent is left to infer usage solely from the verb, which is minimal guidance.

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