Skip to main content
Glama
AutoRepair Cloud MCP server

AutoRepair Cloud MCP server

autorepair_cloud_status

Check your Cotlet.dev account, available credits, and AutoRepair Cloud connection to confirm setup is ready before running repair workflows.

Instructions

Check that your Cotlet.dev account and AutoRepair Cloud are ready: account, credits and AutoRepair Cloud connection.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/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. It usefully enumerates the three areas inspected (account, credits, connection), implying a read-only diagnostic, but says nothing about whether it requires authentication, whether the call itself consumes credits, or how failures surface. For a zero-parameter read check this is acceptable but thin.

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 with the actionable verb first and the checks enumerated after the colon. There is minor redundancy between 'your Cotlet.dev account' and the trailing 'account', but no filler sentences.

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 zero-parameter status tool with no annotations and no output schema, the enumeration of account, credits, and connection effectively communicates what the response will report on. What remains unstated — result format, pass/fail semantics, auth requirements — is modest given the tool's simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so there is no parameter semantics to explain; the baseline for a zero-param tool applies. The description adds nothing misleading about inputs.

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 ('Check') and names the concrete targets: Cotlet.dev account, credits, and the AutoRepair Cloud connection. That is enough to distinguish it from the sibling UI-interaction tools (click, close, open, read, type), which act on the AutoRepair Cloud interface rather than reporting readiness, though it never explicitly contrasts itself with them.

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?

The framing 'Check that your ... are ready' implies a preflight/diagnostic use case before invoking other tools, but it never states when to call it, how often, or what to do with a failure. No alternative or exclusion is named, so guidance is implied rather than explicit.

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