BocaRoss

Chercher des professionnels de l’automobile

chercher_pros

Read-onlyIdempotent

Trouve des professionnels indépendants de l’automobile (garage, carrosserie, pare-brise, contrôle technique, lavage et detailing) autour d’une commune de France, ou autour de l’utilisateur (« près de moi », « autour de moi ») quand l’assistant transmet sa position approximative. À utiliser dès qu’un utilisateur cherche un garage, un carrossier, un centre de contrôle technique, un pare-brise ou un detailing près d’une ville ou près de lui. Rend pour chacun : nom, adresse, distance, téléphone, note Google, horaires du jour, ouvert maintenant ou non, et l’URL de sa fiche BocaRoss. Ne réserve rien.

Input Schema

TableJSON Schema

Name	Required	Description
`ville`	No	La commune, en français, telle que l’utilisateur la dit (ex. « Lille », « Marcq-en-Barœul », « Villeneuve d’Ascq »). À omettre quand l’utilisateur dit « près de moi » sans nommer de commune : l’outil prend alors la position approximative transmise par l’assistant, ou demande la commune.
`limite`	No
`metier`	Yes	mecanique-auto = garage, entretien, réparation, pneus, freins, vidange, diagnostic. carrosserie = carrosserie, peinture, débosselage, sinistre. pare-brise = vitrage, impact, remplacement de pare-brise. controle-technique = contrôle technique, contre-visite. detailing-auto = lavage, nettoyage, detailing, rénovation esthétique, céramique, PPF.
`rayon_km`	No	Rayon de recherche autour de la commune. Par défaut, celui de la page du site, qui se resserre là où les professionnels sont nombreux.
`ouvert_samedi`	No	Ne garder que les professionnels qui ouvrent le samedi.

Output Schema

TableJSON Schema

Name	Required	Description
`total`	No
`metier`	No
`commune`	No
`rayon_km`	No
`resultats`	No
`suggestions`	No
`se_deplacent`	No
`page_annuaire`	No	La page de l’annuaire BocaRoss pour ce métier et cette commune.
`commune_inconnue`	No
`position_approchee`	No	Vrai quand la commune vient de la position approximative transmise par l’assistant (« près de moi »).

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 21, 2026

changedInput schema / properties / ville / description

Previous value: -"La commune, en français, telle que l’utilisateur la dit (ex. « Lille », « Marcq-en-Barœul », « Villeneuve d’Ascq »)."New value: +"La commune, en français, telle que l’utilisateur la dit (ex. « Lille », « Marcq-en-Barœul », « Villeneuve d’Ascq »). À omettre quand l’utilisateur dit « près de moi » sans nommer de commune : l’outil prend alors la position approximative transmise par l’assistant, ou demande la commune."

changedInput schema / required

Previous value: -[
-  "metier",
-  "ville"
-]New value: +[
+  "metier"
+]

addedOutput schema / properties / position_approchee

Added value: +{
+  "description": "Vrai quand la commune vient de la position approximative transmise par l’assistant (« près de moi »).",
+  "type": "boolean"
+}

First observedOct 20, 2026

TDQS

A4/5.0

Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds useful behavior beyond that: it lists what each result includes and explicitly says “Ne réserve rien” (does not book), clarifying that this is a search-only operation.

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

Conciseness4/5

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

The description is front-loaded with the purpose, followed by usage and result content, so it is easy to scan. However, the sentence listing returned fields duplicates information already available in the output schema, which slightly reduces conciseness.

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?

Given the annotations, the 80% schema coverage, and the presence of an output schema, the description is complete enough for an agent to call the tool correctly. It covers the search scope, location behavior, business types, and a clear no-booking constraint.

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 80%, so the schema already documents the parameters well enough. The description reinforces the optional location semantics (“près de moi” uses approximate position), but it does not add substantial meaning beyond what the schema and enum descriptions already provide.

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?

The description gives a specific verb (“Trouve”) and a clear resource (“professionnels indépendants de l’automobile”), enumerating the relevant business types. It does not explicitly distinguish this search tool from the sibling detail tool fiche_pro, so it falls short of a 5 under the rubric.

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 explicitly tells the agent to use the tool whenever a user searches for a garage, body shop, inspection center, windshield service, or detailing near a city or near themselves. It provides clear context but does not state when not to use it or name the sibling alternative.

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

All BocaRoss 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?