Skip to main content
Glama

Mechanic Atlas Auto Manual

Get A Free Access Key

get_access

Make a free access key for the full manual from the person's email. The first 20 cars are free. Shows the key once, so the person should save it. Ask for their email; never make one up.

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": {
      "email": "<email>"
    },
    "name": "get_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesThe person's own email

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (readOnly=false, non-idempotent, non-destructive), the description discloses two important behaviors: the key is displayed only once and must be saved, and there is a free-tier limit of 20 cars. That 'shown once' warning is exactly the kind of irreversible-consumption context the annotations cannot convey. It does not state what happens when the quota is exhausted or on repeated calls.

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?

Four short sentences, front-loaded with the action and resource, then the quota, the save-it warning, and the input rule. No wasted wording; 'The first 20 cars are free' is slightly ambiguous about what counts as a car but is still economical.

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 one-parameter tool with no output schema, the description covers the essential behavior: what gets produced, that it is shown once, the free-tier limit, and the input requirement. Missing only edge-case behavior (quota exceeded, re-issuance), which keeps it short of a 5.

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?

With a single parameter at 100% schema coverage, the schema already documents the email field as 'The person's own email.' The description reinforces this with 'never make one up,' adding a mild integrity constraint, but contributes no new format or validation detail beyond the schema.

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 names a specific verb and resource — making a free access key that unlocks the full manual — and ties it to an email input, so it is distinguishable from read-only siblings like full_manual. It does not explicitly name an alternative, but the purpose is unambiguous.

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?

It gives an operational instruction ('Ask for their email; never make one up') that shapes how the tool is invoked, and 'for the full manual' implies when a key is needed. It does not say when to call this instead of a sibling or what to do if the person already has a key, leaving tool-selection guidance implied rather than stated.

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