Skip to main content
Glama

CarHunt

by fr.carhunt

Estimer le prix d'une voiture (gratuit)

estimate_car_price
Read-only

Estimate the market price of a used car in France. Estimation de prix basée sur les annonces comparables réelles du marché français : bon prix (Q1), valeur juste (médiane), prix haut (Q3), indice de confiance et annonces similaires. Le kilométrage est facultatif : sans lui, l'estimation part du kilométrage médian des annonces comparables et le signale dans note. Sans compte : 3 estimations/jour par IP. Avec clé personnelle Premium/Pro : quota du plan (15/jour ou illimité).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
makeYesMarque, ex. RENAULT
yearYesAnnée-modèle
modelYesModèle, ex. CLIO
energyNoEssence, Diesel, Électrique, Hybride (optionnel)
gearboxNoManuelle ou Automatique (optionnel)
mileageNoKilométrage en km. Second facteur de prix après l'âge : le donner quand on le connaît. Si l'utilisateur ne l'a pas précisé, OMETTEZ ce paramètre plutôt que d'inventer une valeur — l'estimation utilisera alors le kilométrage médian des annonces comparables et le signalera dans `note` (à répercuter à l'utilisateur).

TDQS

A4.5/5.0
Behavior5/5

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

The description discloses methodology (based on comparable real ads), output components, optional mileage behavior (uses median and signals in note), and rate limits. This goes well beyond the readOnlyHint annotation, providing rich behavioral context for the agent.

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 concise and front-loaded with the main purpose, followed by essential details. Every sentence contributes value—methodology, optional mileage, and rate limits—with no redundancy or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description fully explains what the tool returns (Q1, median, Q3, confidence, similar ads) even without an output schema. It also covers edge cases (missing mileage) and quota behavior, making it complete for agent use.

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 descriptions cover 100% of parameters and already explain each field, including detailed guidance on mileage. The tool description adds no new parameter-specific meaning beyond what the schema provides, so baseline 3 is appropriate.

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 'Estimate the market price of a used car in France' with a specific verb and resource. It further details the output (Q1, median, Q3, confidence index, similar ads), distinguishing it from sibling tools like search_used_cars or car_market_stats.

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 provides clear context on when to use the tool (for pricing a used car) and includes usage limits (3/day without account, quota with key). However, it doesn't explicitly contrast with alternatives or state when not to use it, though sibling tools are clearly different.

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

All CarHunt toolsInspect
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