Skip to main content
Glama

skiddle_click

Clicks a numbered element on the current Skiddle page to act on a specific item identified in the last read.

Instructions

Click a numbered element on the current Skiddle 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": "skiddle_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesElement number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/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 for an action that mutates page state. It does not say what a click does (navigate, submit, toggle), whether it waits for a page load, what happens if the element number is stale, or what the tool returns.

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 short sentence that is front-loaded with the action and free of filler. Its brevity comes at the cost of substance, but nothing in it is redundant or misplaced.

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 browser action with no output schema, the definition is minimally sufficient: the agent knows what to pass and what it will act on. It is thin on post-click behavior and failure modes, which matter for an unannotated state-changing tool, but the small surface area keeps the gap tolerable.

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 description coverage is 100% and the single parameter already documents that the integer is an element number from the last read. The description's phrase 'numbered element' reinforces the provenance of that number but adds no format or constraint details 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 specific verb (click) and a specific resource (a numbered element on the current Skiddle page), which is enough to distinguish it from skiddle_open/close/read at a glance. It does not differentiate itself from skiddle_type, which likely also targets numbered elements, so the sibling boundary is left implicit.

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 explicit guidance on when to click versus when to read, type, or open. The only hint about usage comes indirectly from the schema phrase 'Element number from the last read,' which implies a read-then-click workflow but is never stated in the description itself.

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