Skip to main content
Glama

swift_galleries_click

Clicks a numbered element on the current Swift Galleries page using the element number from the last read, enabling agents to interact with page controls.

Instructions

Click a numbered element on the current Swift Galleries 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": "swift_galleries_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?

With no annotations, the description carries the full disclosure burden. It does not say whether the click mutates state, navigates to a new page, submits a form, or what happens to the previously read element list afterwards — all critical for an agent deciding to invoke an irreversible browser action.

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 with the action front-loaded and no wasted wording. It is efficient, though its terseness contributes to the missing behavioral detail noted elsewhere.

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 a browser-automation click with no annotations and no output schema, an agent needs to know the resulting page state and how to recover the new element numbering. The description says nothing about post-click effects, so it is incomplete relative to the tool's actual complexity.

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 schema already documents the single parameter as the element number from the last read, with a minimum of 1. The description adds nothing beyond that, so the baseline 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?

States a concrete verb ("click") and a concrete resource ("a numbered element on the current Swift Galleries page"), which distinguishes it from siblings like swift_galleries_type and swift_galleries_read. It stops short of explicitly naming how it differs from the other interaction tools, but the action 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 schema note "Element number from the last read" suggests this must follow swift_galleries_read, and "current page" hints at a page-state prerequisite. There is no explicit when-to-use, no when-not-to-use, and no mention of swift_galleries_type as the alternative for text entry.

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