Skip to main content
Glama

zanda_click

Clicks a numbered element on the current Zanda page, enabling an agent to select visible page controls by their last-read element number.

Instructions

Click a numbered element on the current Zanda 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": "zanda_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.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, and it says nothing about what a click does beyond the bare verb: whether it navigates, submits a form, mutates state, or is reversible. It also omits what happens on an invalid or stale element number, which is the most likely failure mode for an indexed-element interaction.

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?

One sentence, front-loaded with the verb and the object, with zero filler. It is efficient, though the extreme terseness leaves no room for the sequencing or side-effect context the tool actually needs.

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 an interactive UI-driving tool with no annotations, no output schema, and real side effects, the description is too thin: it does not state what the click triggers, whether a fresh read is required first, or what the agent gets back. The only completeness it offers is naming the page context.

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?

Schema coverage is 100% and the single parameter already documents itself as 'Element number from the last read', so the schema is doing the heavy lifting. The description reinforces that the target is a numbered element, but adds no format, range, or staleness guidance beyond the schema.

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 concrete verb (click) and a concrete target (a numbered element on the current Zanda page), which is enough to distinguish it from zanda_type and zanda_read without opening their schemas. It stops short of explicitly naming those siblings or stating how the interaction differs, so it is clear but not maximally differentiating.

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?

There is no explicit when-to-use or when-not-to-use guidance and no mention of alternatives such as zanda_type or zanda_close. The only usage signal is indirect: the parameter is described as coming 'from the last read', which implies a read-then-click sequence but leaves the agent to infer it.

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