Skip to main content
Glama
AutoRepair Cloud MCP server

AutoRepair Cloud MCP server

autorepair_cloud_click

Use the element number from the last page read to click a specific control on the current AutoRepair Cloud page, enabling navigation and workflow actions.

Instructions

Click a numbered element on the current AutoRepair Cloud 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": "autorepair_cloud_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, yet it says nothing about what a click does (navigation, form submission, irreversible action), whether it waits for the page to settle, or how stale/invalid element numbers are handled. 'Current page' weakly signals statefulness but leaves the agent guessing about side effects for a mutating UI action.

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?

One short sentence with the action and target front-loaded and zero filler. Nothing is wasted, though the brevity is also the source of the informational gaps scored 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 stateful browser-automation click with no annotations and no output schema, the definition leaves out the essential contract: what the click triggers, what the agent sees afterward, and how to recover from a failed click. It is enough to guess the call shape but not enough to call it safely or interpret results.

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?

There is a single parameter with 100% schema description coverage that already explains it is the 'Element number from the last read.' The description adds no syntax, indexing, or validity 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 gives a specific verb ('Click') and resource ('a numbered element on the current AutoRepair Cloud page'), which clearly separates it from siblings like autorepair_cloud_read or autorepair_cloud_type by name. It does not explicitly state how it differs from other interaction tools, but the verb+object pairing 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance, no prerequisites, and no mention of alternatives such as autorepair_cloud_read to obtain element numbers or autorepair_cloud_type for text entry. The only hint is 'current page', which implies a state dependency but never states it as a rule.

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