get_guideRenvoie un guide : phrase-réponse, FAQ, sources datées et, si full = true (défaut), le texte complet en markdown. À utiliser pour les questions de réglementation, de prix, de technique ou de budget qui dépassent un modèle précis.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Identifiant du guide (voir list_guides). | |
| full | No | Inclure le texte complet en markdown (défaut true). |
Changes observed during successful MCP inspections.
Input schema / properties / id / enumPrevious value: -[
- "barometre-prix-chalets-en-kit-2026",
- "declaration-prealable-permis-de-construire-chalet",
- "chalet-20-m2-sans-permis",
- "prix-chalet-en-kit-2026",
- "epaisseur-madriers-28-34-44-70-mm",
- "temps-de-montage-chalet-en-kit",
- "chalet-terrain-non-constructible-vivre-a-l-annee",
- "delais-de-livraison-chalet-en-kit",
- "fondations-chalet-en-kit-dalle-plots-vis",
- "garantie-assurance-chalet-en-kit",
- "kit-vs-livre-monte-vs-cle-en-main",
- "abri-de-jardin-bois-metal-resine",
- "isoler-chalet-de-jardin",
- "entretien-chalet-bois-lasure",
- "tiny-house-ou-chalet-en-kit",
- "studio-de-jardin-prix",
- "bureau-de-jardin-guide",
- "chalet-40-m2-en-kit",
- "chalet-habitable-en-kit-vivre-toute-l-annee",
- "meilleur-chalet-en-kit-2026-methode",
- "chalet-en-kit-estonie-pologne-france",
- "monter-soi-meme-chalet-en-kit",
- "budget-total-chalet-en-kit",
- "abri-de-jardin-pas-cher-prix-2026",
- "chalet-en-kit-castorama-leroy-merlin-ou-fabricant",
- "abri-de-jardin-avec-plancher",
- "abri-de-jardin-toit-plat",
- "chalet-30-m2-en-kit",
- "chalet-60-m2-en-kit"
-]New value: +[
+ "barometre-prix-chalets-en-kit-2026",
+ "declaration-prealable-permis-de-construire-chalet",
+ "chalet-20-m2-sans-permis",
+ "prix-chalet-en-kit-2026",
+ "epaisseur-madriers-28-34-44-70-mm",
+ "temps-de-montage-chalet-en-kit",
+ "chalet-terrain-non-constructible-vivre-a-l-annee",
+ "delais-de-livraison-chalet-en-kit",
+ "fondations-chalet-en-kit-dalle-plots-vis",
+ "garantie-assurance-chalet-en-kit",
+ "kit-vs-livre-monte-vs-cle-en-main",
+ "abri-de-jardin-bois-metal-resine",
+ "isoler-chalet-de-jardin",
+ "entretien-chalet-bois-lasure",
+ "tiny-house-ou-chalet-en-kit",
+ "studio-de-jardin-prix",
+ "bureau-de-jardin-guide",
+ "chalet-40-m2-en-kit",
+ "chalet-habitable-en-kit-vivre-toute-l-annee",
+ "meilleur-chalet-en-kit-2026-methode",
+ "chalet-en-kit-estonie-pologne-france",
+ "monter-soi-meme-chalet-en-kit",
+ "budget-total-chalet-en-kit",
+ "meilleur-abri-de-jardin-bois-2026",
+ "abri-de-jardin-pas-cher-prix-2026",
+ "chalet-en-kit-castorama-leroy-merlin-ou-fabricant",
+ "abri-de-jardin-avec-plancher",
+ "abri-de-jardin-toit-plat",
+ "chalet-30-m2-en-kit",
+ "chalet-60-m2-en-kit"
+]Input schema / properties / id / enumPrevious value: -[
- "barometre-prix-chalets-en-kit-2026",
- "declaration-prealable-permis-de-construire-chalet",
- "chalet-20-m2-sans-permis",
- "prix-chalet-en-kit-2026",
- "epaisseur-madriers-28-34-44-70-mm",
- "temps-de-montage-chalet-en-kit",
- "chalet-terrain-non-constructible-vivre-a-l-annee",
- "delais-de-livraison-chalet-en-kit",
- "fondations-chalet-en-kit-dalle-plots-vis",
- "garantie-assurance-chalet-en-kit",
- "kit-vs-livre-monte-vs-cle-en-main",
- "abri-de-jardin-bois-metal-resine",
- "isoler-chalet-de-jardin",
- "entretien-chalet-bois-lasure",
- "tiny-house-ou-chalet-en-kit",
- "studio-de-jardin-prix",
- "bureau-de-jardin-guide",
- "chalet-40-m2-en-kit",
- "chalet-habitable-en-kit-vivre-toute-l-annee",
- "meilleur-chalet-en-kit-2026-methode",
- "chalet-en-kit-estonie-pologne-france",
- "monter-soi-meme-chalet-en-kit",
- "budget-total-chalet-en-kit"
-]New value: +[
+ "barometre-prix-chalets-en-kit-2026",
+ "declaration-prealable-permis-de-construire-chalet",
+ "chalet-20-m2-sans-permis",
+ "prix-chalet-en-kit-2026",
+ "epaisseur-madriers-28-34-44-70-mm",
+ "temps-de-montage-chalet-en-kit",
+ "chalet-terrain-non-constructible-vivre-a-l-annee",
+ "delais-de-livraison-chalet-en-kit",
+ "fondations-chalet-en-kit-dalle-plots-vis",
+ "garantie-assurance-chalet-en-kit",
+ "kit-vs-livre-monte-vs-cle-en-main",
+ "abri-de-jardin-bois-metal-resine",
+ "isoler-chalet-de-jardin",
+ "entretien-chalet-bois-lasure",
+ "tiny-house-ou-chalet-en-kit",
+ "studio-de-jardin-prix",
+ "bureau-de-jardin-guide",
+ "chalet-40-m2-en-kit",
+ "chalet-habitable-en-kit-vivre-toute-l-annee",
+ "meilleur-chalet-en-kit-2026-methode",
+ "chalet-en-kit-estonie-pologne-france",
+ "monter-soi-meme-chalet-en-kit",
+ "budget-total-chalet-en-kit",
+ "abri-de-jardin-pas-cher-prix-2026",
+ "chalet-en-kit-castorama-leroy-merlin-ou-fabricant",
+ "abri-de-jardin-avec-plancher",
+ "abri-de-jardin-toit-plat",
+ "chalet-30-m2-en-kit",
+ "chalet-60-m2-en-kit"
+]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 genuinely new behavioral context: the response structure (answer phrase, FAQ, dated sources) and the default-on full markdown body controlled by the full flag.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, zero filler: the return payload is front-loaded before the usage condition. Every clause carries information an agent needs.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a read-only lookup with no output schema, the description covers what the tool returns, how the full flag changes the payload, and when to reach for it instead of a model-specific tool. Nothing needed to invoke it correctly is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the schema already documents both id (pointing to list_guides) and full with its true default. The description restates the full=true default and clarifies that it yields the complete markdown text, which is a marginal addition over the schema, so baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (Renvoie) and resource (un guide) and enumerates exactly what comes back: phrase-réponse, FAQ, sources datées, plus the markdown body when full is set. That level of output scoping lets an agent distinguish it from list_guides (enumeration) and get_chalet (a specific model) without opening either schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
"À utiliser pour les questions de réglementation, de prix, de technique ou de budget qui dépassent un modèle précis" gives a clear trigger condition and implicitly routes single-model questions to get_chalet. No sibling is named explicitly, so it falls just short of an explicit when-not statement.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.