Skip to main content
Glama

styleseat_click

Clicks a numbered element on the current StyleSeat page to interact with controls identified in the last read.

Instructions

Click a numbered element on the current StyleSeat 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": "styleseat_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.3/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 behavioral burden. It states that a click occurs but does not disclose side effects such as navigation, submission, page changes, waiting behavior, or what happens if the element number is invalid, leaving significant gaps for an action tool.

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

Conciseness5/5

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

The description is a single front-loaded sentence with no filler or repetition. Every word contributes to identifying the action and its target.

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?

The tool is simple, has only one fully documented parameter, and no output schema, so the description is minimally usable. However, with no annotations it should say more about what clicking results in and how failures or page transitions are handled.

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 defines the single parameter as an integer with minimum 1 and the description "Element number from the last read." The tool description adds only "numbered element on the current page," which does not add meaningful format or constraint detail beyond the schema, 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 uses a specific verb, "Click," and a specific target, "a numbered element on the current StyleSeat page," so an agent can distinguish this action from read, type, open, or close. It does not explicitly name the sibling tools, but the verb sufficiently separates it from the other operations.

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 implied by "on the current StyleSeat page" and by the schema note that the element number comes from the last read, which suggests this tool should follow a read operation. It does not explicitly state when to use this versus styleseat_read or styleseat_type, nor does it give exclusions or prerequisites.

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