Skip to main content
Glama

Search used cars

search_marketplace
Read-onlyIdempotent

Search live used vehicle listings on the MotifyMe marketplace (UK dealers). Returns up to 20 results per call with price, mileage, dealer and the public listing url.

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

Input Schema

NameRequiredDescriptionDefault
makeNoe.g. Ford
sortNonewest, price_asc, price_desc or mileage_asc
townNodealer town
limitNo1-20, default 10
modelNoe.g. Fiesta
dealerNodealer slug or name fragment
offsetNofor paging
max_yearNofirst registration year
min_yearNofirst registration year
body_typeNoe.g. Hatchback, SUV, Estate
fuel_typeNoe.g. Petrol, Diesel, Electric, Petrol Hybrid
max_priceNoGBP
min_priceNoGBP
max_mileageNomiles
transmissionNoManual or Automatic

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond them by disclosing the result cap ('up to 20 results per call') and the returned fields (price, mileage, dealer, public listing url), although it does not explain paging behavior or whether the 20 cap overrides the limit parameter.

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, no filler, with the resource and scope front-loaded and the return shape trailing. Every clause carries information an agent would otherwise have to guess.

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 15-parameter, zero-required search tool with no output schema, the description covers the source, the result cap and the key returned fields, which is enough to invoke it sensibly. It stops short of describing default behavior when no filters are supplied or how offset interacts with the cap, which would have closed the remaining gap.

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 description coverage is 100% across all 15 parameters, including the enum for sort and unit hints (GBP, miles), so the schema does the heavy lifting. The description adds essentially no parameter-level meaning beyond loosely restating the result cap, which is baseline 3.

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 and resource ('Search live used vehicle listings on the MotifyMe marketplace') plus scope ('UK dealers'), so the agent knows exactly what is searched. It does not differentiate from the closest sibling, ai_car_search, which is a natural-language alternative an agent could easily confuse it with.

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

Usage Guidelines3/5

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

Usage is implied by the description (free-text/structured listing search with paging via limit/offset), but there is no explicit when-to-use or when-not-to-use guidance. Nothing tells the agent to prefer this over ai_car_search or get_listing.

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