Skip to main content
Glama

wanderlog_click

Clicks a numbered element on the current Wanderlog page to select or activate the matching control after reading the page. Use the element number from the last read to perform page actions.

Instructions

Click a numbered element on the current Wanderlog page.

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": {
      "element": "<element>"
    },
    "name": "wanderlog_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesElement number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/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 behavioral burden, and it discloses almost nothing. It does not say what clicking does (navigate, submit, toggle), whether it mutates application state, whether the page's element numbering is invalidated afterward, or whether a subsequent read is required.

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; the target is stated before any qualifiers. It is efficient, though its brevity contributes to the behavioral gaps noted elsewhere.

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 one-parameter interaction tool with no output schema, the definition is minimally sufficient to call correctly. It is incomplete about what an agent should expect after the click, which matters for a state-changing browser action with no annotations to lean on.

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?

There is one parameter at 100% schema coverage, and the schema already explains it as 'Element number from the last read.' The description's 'numbered element' restates the same idea without adding format, range, or staleness semantics, so the baseline of 3 applies.

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 specific verb (click) and a specific target (a numbered element on the current Wanderlog page), which is concrete enough to act on. It is not differentiated from siblings by name (e.g., why click rather than type or open), but the resource is unambiguous.

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 only implied: the phrase 'on the current Wanderlog page' hints that a page must already be loaded and elements numbered, presumably by wanderlog_read. There is no explicit when-to-use, no statement of prerequisites, and no guidance on when to choose wanderlog_type or wanderlog_open instead.

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