Skip to main content
Glama

Search cars by describing them

ai_car_search
Read-onlyIdempotent

Describe the used car you want in plain English, for example "diesel estate under 8000 no older than 8 years" or "2.0L Audi Q3 automatic", and get matching live MotifyMe marketplace listings. If nothing matches every detail, the closest real cars are returned and the ignored details are listed.

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": {
      "request": "<request>"
    },
    "name": "ai_car_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo1-20, default 10
requestYesPlain-English description of the car wanted

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds real behavioural context beyond that: results come from live marketplace inventory, and matching is fuzzy — when details cannot all be satisfied the closest real cars are returned and the ignored criteria are reported back, which prevents an agent from misreading a partial match as an exact one.

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

Conciseness5/5

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

Two sentences, front-loaded with the core action and immediately followed by illustrative examples, then the one non-obvious caveat about partial matches. No restatement of the title, no 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?

With no output schema, the description carries the burden of saying what comes back, and it does name the return type (live marketplace listings, plus a report of ignored details). It stops short of describing result shape or ordering, though the 'limit' parameter in the schema implies a bounded result set.

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%, so the baseline is 3, but the description earns a step up by showing what a good 'request' string actually looks like ("diesel estate under 8000 no older than 8 years"), conveying that the field is unstructured prose rather than a filter DSL. The 'limit' parameter is left entirely to the schema, which documents it adequately.

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?

States a specific verb+resource: natural-language car search returning live MotifyMe marketplace listings, illustrated with two concrete query examples. It is clear what the tool does, but it never distinguishes itself from the sibling search_marketplace, so an agent cannot tell which search path to pick from this text alone.

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?

The examples implicitly teach the calling convention (free-text description, attributes like fuel, body style, price ceiling, age, engine, transmission), which is genuine usage guidance. It does not, however, state when not to use it or name any alternative such as search_marketplace or list_makes_and_models.

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