Skip to main content
Glama

Mechanic Atlas Auto Manual

Repair Jobs For A Vehicle

repair_jobs
Read-onlyIdempotent

List the repair and maintenance jobs that apply to a vehicle, grouped by section, with a difficulty rank from 1 (easy) to 5 (hardest). Titles only.

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": {
      "make": "<make>",
      "model": "<model>"
    },
    "name": "repair_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
makeYesMake, for example Toyota
yearNoModel year, for example 2015
modelYesModel, for example Camry
sectionNoOptional section filter, for example Brakes or Cooling

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, non-open-world behavior, so the safety profile is covered. The description adds real value beyond them by disclosing the output shape (section grouping, 1-5 difficulty ranking, titles only) and that the lookup is vehicle-scoped.

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?

A single sentence with zero filler; the scope, the grouping, the ranking scale, and the titles-only limitation are all front-loaded and each clause adds information.

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?

With no output schema, the description does the needed work of explaining what comes back and how it is organized. Minor gaps remain: it does not say whether year is required for accurate matching or what happens when no jobs are found.

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 description coverage is 100%, with per-field examples for make, model, year, and section, so the schema carries the parameter burden. The description adds nothing about how make/model/year combine or how the section filter interacts with grouping, so 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?

The description gives a specific verb ('List') and resource ('repair and maintenance jobs that apply to a vehicle'), plus the shape of the result. 'Titles only' implicitly separates it from siblings like repair_guides or full_manual, but no sibling is named explicitly, so an agent must infer the boundary.

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 'titles only' and 'grouped by section' framing suggests this is a discovery/overview call before drilling into guides or the full manual. There is no explicit when-to-use, when-not-to-use, or named alternative.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources