CarHunt

Recherche pro complète (clé API)

pro_search

Read-only

Full professional search with deal-score, 50 results/page, incremental polling. Recherche complète pour les professionnels : deal-score de sous-cote sur chaque annonce, tri deal_score, filtres finition/motorisation/fraîcheur, pagination, polling incrémental (since). Requiert une clé API CarHunt Pro (plan Business). Consomme le quota mensuel de véhicules de l'organisation.

Input Schema

TableJSON Schema

Name	Required	Description
`make`	No	Marque, ex. VOLKSWAGEN, PEUGEOT, BMW
`page`	No	Page de résultats (défaut 1)
`sort`	No
`limit`	No	Résultats par page, max 50 (défaut 25)
`model`	No	Modèle commercial, ex. GOLF, 308, SERIE 1 — les familles sont expansées (« GOLF » matche GOLF, GOLF SW…)
`since`	No	Timestamp ISO — ne renvoyer que les annonces découvertes après (polling incrémental)
`energy`	No	Énergies séparées par des virgules : Essence,Diesel,Électrique,Hybride
`region`	No	Région française : ile-de-france (ou idf), paca, bretagne, occitanie, normandie… Exclusif avec departments.
`gearbox`	No	Boîtes séparées par des virgules : Manuelle,Automatique
`finition`	No	Finition normalisée, ex. R-Line, GT Line
`year_max`	No
`year_min`	No	Année-modèle minimum
`price_max`	No	Prix maximum en euros
`price_min`	No	Prix minimum en euros
`departments`	No	Codes départements, ex. ["33", "24", "40"]
`mileage_max`	No	Kilométrage maximum
`mileage_min`	No
`seller_type`	No	Vendeur professionnel ou particulier (couverture partielle)
`motorization`	No	Code moteur, ex. « 2.0 TDI » — match souple
`min_deal_score`	No	Plancher de score de sous-cote (50 = prix médian marché)
`seen_within_days`	No	Ne renvoyer que les annonces re-vues par les scrapers dans les N derniers jours (anti-annonces retirées ; recommandé 7)

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses critical side-effects: it 'Consomme le quota mensuel de véhicules de l'organisation' and requires a paid API key. It also reveals behavioral details like incremental polling (since) and the 50-results-per-page cap. This goes well beyond the annotations.

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 compact, two sentences, with the key value proposition upfront. Every clause adds information: features, filtering options, pagination, polling, authentication, and quota impact. No redundant wording.

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?

Given the tool's complexity (21 parameters, no output schema), the description covers the essential behavioral aspects: deal-score, filters, pagination, incremental polling, auth, and quota. It does not explicitly describe the response structure, but since it is a search tool, the return shape is partly inferable. The description is sufficient for an agent to select and use the tool correctly.

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?

With 86% schema description coverage, the schema already documents most parameters individually. The description adds meaningful context by linking parameters to the deal-score concept (min_deal_score, sort) and explaining incremental polling (since). It also clarifies pagination behavior (limit max 50). A few undocumented parameters remain, but the high schema coverage keeps this at a strong score.

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 clearly states the tool's purpose: 'Full professional search with deal-score, 50 results/page, incremental polling.' It specifies the resource (search), target audience (professionals), and distinct features (deal-score, polling) that differentiate it from basic search tools. The scope is precise and actionable.

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?

The description provides contextual prerequisites (requires CarHunt Pro API key, consumes monthly quota) but does not explicitly state when to use this tool versus alternatives like search_used_cars or pro_deals. Usage is implied for professional searches needing deal-scores, but no exclusions or alternatives are mentioned.

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

All CarHunt tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0

Disambiguation4/5

Tools are mostly distinct, with slight overlap between pro_search and search_used_cars, but descriptions differentiate based on professional features and deal scores. Pro_deals and pro_search also have different purposes.

Naming Consistency5/5

All tool names use snake_case with a consistent pattern: descriptive nouns for consumer tools (car_market_stats, estimate_car_price, search_used_cars) and pro_ prefix for professional tools (pro_search, pro_deals, pro_watchlist_create). No mixing of conventions.

Tool Count5/5

10 tools is well-scoped for a car market API covering both consumer and professional needs. It is not too few or too many, and each tool serves a clear purpose.

Completeness4/5

The tool set covers core operations: market stats, price estimation, search, deals, watchlists, and usage. Missing a dedicated tool to retrieve full details of a single listing by ID, but agents can work around using search results.

Resources

Need Help?