Skip to main content
Glama

Get the Before the Lot method

get_method
Read-onlyIdempotent

The Before the Lot method for buying a car: an overview and its seven stages, from setting the budget at home to signing. Each stage says what to collect, what it produces, which guides, tools and email templates apply, and when it's done. Use it to plan a purchase step by step or to see where a step fits; pass a stage id for that stage alone. Returns text with a link to the method's page.

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

Input Schema

NameRequiredDescriptionDefault
stageNoOne stage id; leave out for the whole method

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world behavior, so the safety profile needs no restating. The description adds real context beyond the annotations: the content structure of each stage (what to collect, what it produces, applicable guides/tools/templates, completion criteria) and the return format ('text with a link to the method's page').

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?

Three sentences, front-loaded with the resource and scope, then stage contents, then usage. The middle enumeration of stage contents is slightly wordy but each sentence carries information an agent needs; nothing is filler.

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 single-parameter, read-only lookup with no output schema, the description covers the resource, the scoping behavior, the stage-level content, and the return format. It is nearly complete; only fine details like error behavior for invalid stage ids are absent, which is minor here.

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?

Schema coverage is 100% and the enum is fully documented in the schema, so the baseline is 3. The description adds a modest amount of meaning by clarifying that a stage id returns that stage alone and that omitting it yields the whole method — reinforcing the default behavior rather than merely repeating 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 resource (the Before the Lot method) and specifies its scope: an overview plus seven stages from budgeting to signing. It is clearly distinct from the calculator/analysis siblings by being the only method-overview tool, though it does not explicitly contrast itself with any sibling.

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

Usage Guidelines4/5

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

It states two concrete use cases — planning a purchase step by step, or seeing where a step fits — and explains when to pass a stage id versus leaving it out. It stops short of naming alternatives or exclusions, so a 4 rather than a 5.

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