Skip to main content
Glama
AutoRepair Cloud MCP server

AutoRepair Cloud MCP server

autorepair_cloud_guide

Learn how to navigate AutoRepair Cloud and find the sign-in link before starting repair quotes, workshop bookings, parts, or shop reports. Call this guide first.

Instructions

How to work in AutoRepair Cloud (repair quotes, workshop bookings, parts and shop reports): its screens and the sign-in link. Call this first.

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_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in AutoRepair Cloud, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full behavioral burden. It discloses that the guide covers screens and provides a sign-in link, but it does not clarify whether it merely returns instructions versus performing authentication, nor does it describe side effects, expiration, or return format.

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?

Two tightly written sentences front-load the purpose and end with the critical sequencing instruction. Parenthetical scope examples add useful detail without waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a low-complexity guide tool with one optional parameter and no output schema, the description is largely sufficient: it states scope, usage timing, and some expected content. It could still say more about what calling it returns and whether it is safe to call repeatedly.

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?

The single optional task parameter is fully documented by the schema, which explains it as the user's goal in their own words. The description does not mention the task parameter or add meaning 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 clearly identifies this as a guide for working in AutoRepair Cloud, covering repair quotes, workshop bookings, parts, shop reports, screens, and the sign-in link. It is distinguishable from task-specific siblings, though it could more explicitly state that it is orientation material rather than an action tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

"Call this first" gives explicit sequencing guidance: use this guide before attempting other AutoRepair Cloud operations. It does not name alternatives or when not to use it, but the ordering instruction is clear and directly useful.

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