Skip to main content
Glama

grid

Clicks the center of a Vimium-style grid cell on a target window to let agents select GUI elements by row and column.

Instructions

Click the center of a Vimium-style grid cell on the window.

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": {
      "hwnd": "<hwnd>",
      "row": "<row>",
      "col": "<col>"
    },
    "name": "grid"
  }
}

Input Schema

NameRequiredDescriptionDefault
colYes
rowYes
colsNo
hwndYes
rowsNo
dry_runNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, yet it says nothing about safety or side effects. Critically, the schema defaults dry_run to true, meaning the described 'click' does not actually click by default — the description never mentions this, nor does it cover coordinate handling, permissions, or what is returned.

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

Conciseness3/5

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

It is a single front-loaded sentence with no filler, which is structurally fine. However, its brevity comes at the cost of under-specification rather than efficiency, so it cannot earn top marks here.

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

Completeness1/5

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

For a six-parameter action tool with zero schema descriptions, no annotations, and no output schema, the description is far too thin. An agent cannot determine prerequisites, coordinate semantics, the effect of dry_run, or the result of the call from this definition.

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

Parameters1/5

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

Schema description coverage is 0% across six parameters, and the description compensates for none of them: hwnd, row, col, rows, cols, and dry_run are all unexplained. It does not clarify the relationship between row/col (the cell) and rows/cols (the grid dimensions), or that row/col are 1-based, which is the single most error-prone aspect of this call.

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 names a concrete verb ('Click') and a concrete target ('the center of a Vimium-style grid cell on the window'), so the agent knows the action and the object. It does not differentiate itself from siblings like 'click' or 'click_by_id', and it never explains what a 'Vimium-style grid' is or whether a grid must first be displayed before a cell can be clicked.

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 statement of when to reach for this tool versus 'click' or 'click_by_id', no prerequisites (e.g., that a grid must be overlaid first), and no exclusions. The only implied guidance is the word 'grid', which is not enough to route an agent reliably.

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