Crawlora MCP

bringatrailer_suggest

Read-only

Complete a Bring a Trailer search term (1 to 100 characters, for example porsche 911 or 1970s) into make pages, model and generation pages, decades and categories. Era rows carry the decade id and category rows the category id that bringatrailer_results accepts as era and category; make rows can be passed by title as the make parameter. Model rows have no id: use bringatrailer_makes for a model's numeric model_id.

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": {
      "term": "<term>"
    },
    "name": "bringatrailer_suggest"
  }
}

Input Schema

Name	Required	Description	Default
`term`	Yes	Required. Text to complete, 1 to 100 characters (for example porsche 911 or 1970s).

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds real behavioral context annotations can't: the result set is partitioned into typed row kinds (make, model, generation, decade, category) and which of those carry usable ids. It doesn't mention what happens on no matches or any result cap, which is the remaining gap.

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?

Dense and mostly front-loaded: purpose first, then the id-routing instructions. It is close to a run-on sentence chain in the second half, and the '1 to 100 characters' restatement is redundant with the schema, but nothing is padded.

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 an output schema present, the description doesn't need to explain return values, yet it still explains the row types and which ids are or aren't present — the thing an agent actually needs to chain to bringatrailer_results or bringatrailer_makes. Only empty/edge-case behavior is unaddressed.

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 the schema already states the 1–100 character bound and gives the same 'porsche 911 or 1970s' examples. The description repeats that range verbatim rather than adding new meaning about accepted term syntax or matching behavior, so baseline 3 applies.

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

Purpose5/5

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

Opens with a specific verb+resource: 'Complete a Bring a Trailer search term ... into make pages, model and generation pages, decades and categories.' It clearly distinguishes itself from the retrieval siblings (bringatrailer_results, bringatrailer_makes) by being the completion/expansion step rather than the listing step.

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 routes the agent explicitly for two branches: era/category ids feed bringatrailer_results, make rows can go in as the make parameter, and model rows must go to bringatrailer_makes for a model_id. What's missing is an explicit statement of when to call this at all (e.g. 'use before bringatrailer_results when you only have free text rather than ids').

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.