Skip to main content
Glama

salonbridge_click

Clicks a numbered element on the current SalonBridge page to trigger on-page actions in a signed-in SalonBridge account.

Instructions

Click a numbered element on the current SalonBridge 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": "salonbridge_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 supplied, so the description carries the full behavioral burden and does very little with it. It does not say whether clicking navigates to a new page, whether the element numbering becomes stale afterward, what happens on an invalid or out-of-range number, or whether any confirmation or return value is produced. Only 'current page' gives a hint of statefulness.

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 short sentence with the action and target front-loaded and no filler. It is efficient, though the terseness contributes to the behavioral gaps noted elsewhere rather than being a model of completeness.

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-interaction tool with no annotations and no output schema, the definition is thin: nothing is said about page state changes after the click, error handling for stale element numbers, or whether a fresh read is required before the next action. The parameter is fully documented by the schema, but the behavioral envelope an agent needs is missing.

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 baseline applies. The description's phrase 'numbered element' is consistent with the schema but adds no meaning about valid ranges, staleness, or how numbers are assigned.

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 states a specific verb (click) and a specific target (a numbered element on the current SalonBridge page), which is enough to separate it from siblings like salonbridge_read, salonbridge_type, and salonbridge_close. It stops short of explicitly contrasting itself with those siblings, but the action and object are 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 implied rather than stated: the schema's 'Element number from the last read' hints that a read must precede the click, but the description itself gives no when-to-use or when-not-to-use guidance and does not name alternatives such as salonbridge_type for text entry. An agent can infer the workflow but must do the work itself.

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