Skip to main content
Glama

Mechanic Atlas Auto Manual

My Account

my_account
Read-onlyIdempotent

Free pulls left, wallet, membership, the cars unlocked right now, and how to pay.

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": {
      "key": "<key>"
    },
    "name": "my_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesThe person's access key

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description's contribution is enumerating what comes back (balance, membership, unlocked vehicles, payment instructions), which matters because there is no output schema, but it says nothing about auth failure behavior or the fact that results are scoped to the key holder.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence with no waste, but it is compressed to the point of ambiguity — the noun list is front-loaded yet the opening item ('Free pulls left') is cryptic rather than informative. Brevity here costs clarity rather than buying it.

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

Completeness3/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 right thing by listing returned data, and the tool is a simple one-parameter read whose annotations cover safety. Still, a cryptic item like 'free pulls' and the absence of any statement about key scoping leave an agent guessing at part of the payload.

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?

There is a single parameter with 100% schema description coverage ('The person's access key'), so the schema already carries the semantics. The description adds nothing about the key's scope or what access it grants, which is the expected baseline-3 outcome when coverage is complete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a bare list of resources ('free pulls left, wallet, membership, the cars unlocked right now, and how to pay') with no verb and no statement that this is a per-account dashboard read. The resources named (wallet, membership, unlocked cars) do distinguish it from siblings like recalls or repair_guides, but 'free pulls' is unexplained jargon that an agent may not map to a domain concept.

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

Usage Guidelines2/5

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

There is no guidance on when to call this versus alternatives, nor any prerequisite stated. Usage is only implied by the possessive framing ('the cars unlocked right now') that this is the caller's own account snapshot.

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