Skip to main content
Glama

Mechanic Atlas Auto Manual

Repair And Buyer Guides

repair_guides
Read-onlyIdempotent

Find our published repair and buyer guides by make, model, year or topic. Returns titles, links and short summaries.

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": "repair_guides"
  }
}

Input Schema

NameRequiredDescriptionDefault
makeNoMake, for example Toyota
yearNoModel year, for example 2015
modelNoModel, for example Camry
topicNoOptional words to match, for example timing chain

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 and closed-world, so safety is covered; the description adds value by disclosing the return shape (titles, links, short summaries). It leaves one meaningful behavior unstated for a zero-required-parameter search: what happens when no facet is supplied, and whether results are capped or ordered.

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 sentences, no filler: the first states the searchable facets, the second states the return payload. Information is front-loaded and every clause earns its place.

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 read-only search tool with full schema coverage and no output schema, the description covers purpose, facets and return contents adequately. The remaining gap is the no-parameter/behavioral case, which matters given that zero parameters are required.

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 coverage is 100% and each parameter already carries an example, so the schema does the heavy lifting. The phrase "by make, model, year or topic" hints that the facets are alternative selectors rather than all required, but it adds little beyond what the schema examples already convey.

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 and resource ("Find our published repair and buyer guides") plus the facets that select them (make, model, year, topic), so the agent knows exactly what it retrieves. It does not distinguish this from siblings such as factory_manual_links or full_manual, which could plausibly be reached for similar documentation requests.

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: "Find our published ... guides" suggests a faceted search over the site's own content. There is no statement of when to prefer this over factory_manual_links, full_manual, or complaints, and no note that all four parameters are optional and may be combined or omitted.

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