THRIVE Fleet Intelligence

Search the UK van database

search_vans

Read-only

Search THRIVE's database of vans and pickups on sale in the UK, every figure from the manufacturer's UK documents. Filter by text (make, model or size code), powertrain, size class, minimum payload, minimum range and maximum price. Returns up to 25 vans with headline figures; use get_van for the full specification.

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_vans"
  }
}

Input Schema

Name	Required	Description
`query`	No	Words to match in the make, model or version, e.g. 'Transit Custom', 'L2H2', 'Vivaro'
`powertrain`	No
`size_class`	No
`max_price_gbp`	No	List price excluding VAT
`min_payload_kg`	No
`min_range_miles`	No	Official range, electric vans only

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The annotations already establish that this is a read-only, closed-world search. The description adds useful behavior beyond that: results are capped at 25 vans with headline figures, and full specifications require get_van. It does not describe sorting or pagination behavior, which keeps it from a 5.

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?

The description is three tight sentences, front-loaded with purpose and scope before filters and return behavior. Every sentence contributes useful information without 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 six-parameter search tool with no output schema, the description covers purpose, data provenance, filters, result cap, and the path to full details via get_van. It could be more complete by naming the headline figures returned or explaining pagination/sorting, but it is sufficient to invoke the tool correctly.

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?

With 50% schema description coverage, the description partially compensates by naming all six filter concepts: text, powertrain, size class, minimum payload, minimum range, and maximum price. However, most of this restates parameter names rather than adding meaning, and it does not clarify details such as VAT exclusion for price or the electric-only range constraint.

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?

The description states a specific verb and resource: searching THRIVE's database of UK vans and pickups. It also distinguishes the tool from get_van, which is explicitly reserved for full specifications.

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 description gives clear usage context: search to find vans with headline figures, then use get_van for the full specification. It does not explicitly state when not to use the tool or mention other sibling alternatives, but the primary alternative is named.

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

All THRIVE Fleet Intelligence 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.

Resources

Need Help?