Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bringatrailer_suggest

Retrieve Bring a Trailer search-box completions for a term, including makes, models, decades, and categories with IDs to filter result searches.

Instructions

Bring a Trailer search suggestions. Returns Bring a Trailer's search-box completions for a term: 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 make. 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

NameRequiredDescriptionDefault
termYesText to complete

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose the shape of the response (four distinct row classes) plus how each row's id maps into downstream tools. It does not mention limits on the number of suggestions, empty-result behavior, or any auth/rate considerations, which are the remaining gaps.

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 with the core behavior front-loaded and no filler. The third sentence is dense with id-mapping detail but every clause carries actionable information.

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?

No output schema exists, so describing the returned row classes and their id fields is exactly the right compensation, and it is done. Minor incompleteness around result volume and ordering is not material for a completion endpoint.

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 only one parameter and schema description coverage is 100%, so the schema already fully documents it. The description says only 'for a term' / 'completions', adding no format or length constraints beyond the schema, so the baseline 3 applies.

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?

"Returns Bring a Trailer's search-box completions for a term" names a specific verb and resource, then enumerates the row types (make pages, model/generation pages, decades, categories), which is far more informative than a restatement of the name. It distinguishes itself from bringatrailer_makes, but not from bringatrailer_search, so sibling differentiation is only partial.

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 gives concrete routing rules: use the era id and category id with bringatrailer_results, pass make rows by title as make, and use bringatrailer_makes for a numeric model_id. That is real when-to-use guidance, though it never explicitly states when to prefer this over bringatrailer_search.

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

Deploy Server

Other Tools