Skip to main content
Glama
AutoRepair Cloud MCP server

AutoRepair Cloud MCP server

autorepair_cloud_open

Open a page in your signed-in AutoRepair Cloud browser to manage repair quotes, workshop bookings, parts, and shop reports.

Instructions

Open a AutoRepair Cloud page in your signed-in Cloud Browser (default https://autorepaircloud.com/login) to work with repair quotes, workshop bookings, parts and shop reports.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "autorepair_cloud_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://autorepaircloud.com/login

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/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 burden. 'Your signed-in Cloud Browser' usefully implies an existing authenticated session with no credentials needed, but it does not say whether opening a page replaces the current page (destroying prior navigation state), opens a new tab, what happens on an unreachable URL, or what the call returns. For a browser session tool where page state is the core resource, these omissions matter.

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 front-loaded sentence: verb, resource, session context, then the default in parentheses. No filler. Minor grammar slip ('a AutoRepair') and the trailing purpose list ('repair quotes, workshop bookings, parts and shop reports') is decorative rather than actionable, but overall it is tight.

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-optional-parameter tool with full schema coverage and no output schema, the description covers the essentials: what opens, in which session, and the default target. The missing piece an agent would want is session semantics (does this reset the page that click/type/read operate on) and any failure behavior, which the simple schema does not convey.

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?

Only one optional parameter and schema coverage is 100%, so the schema already documents `url` and its default completely. The description restates the default URL but adds no syntax, format, or validation meaning beyond it. 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 specific verb ('Open') and resource ('a AutoRepair Cloud page in your signed-in Cloud Browser'), plus the default target URL. It is distinguishable from the closest sibling, autorepair_cloud_close, and the parenthetical default tells the agent what happens with no argument. It stops short of naming siblings it depends on (click/type/read), so it is clear but not fully differentiated.

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 agent can infer this is the entry point that must precede click/type/read, since those act on an opened page. There is no explicit 'use this first' statement, no guidance on when to open a different URL vs. the default login page, and no exclusions.

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