Skip to main content
Glama

Champs d’une estimation de devis

get_quote
Read-onlyIdempotent

Décrit une estimation de devis Vitef (devis déménagement, diagnostics immobiliers, devis peinture, devis isolation, devis pompe à chaleur, devis chaudière, devis panneaux solaires, devis borne de recharge, devis toiture, devis salle de bain, devis cuisine, devis fenêtres, devis plombier, devis électricien, devis ravalement de façade, devis jardinier, devis ménage à domicile, devis climatisation, devis volets roulants, devis porte d’entrée, devis traitement de l’humidité, devis monte-escalier, devis douche sénior, devis baignoire à porte, devis entretien de pompe à chaleur) : étapes et champs attendus. À appeler avant estimate_quote.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesIdentifiant du devis.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / slug / enum
      Previous value: -[
      -  "demenagement",
      -  "diagnostics-immobiliers",
      -  "peinture",
      -  "isolation",
      -  "pompe-a-chaleur",
      -  "chaudiere",
      -  "panneaux-solaires",
      -  "borne-de-recharge",
      -  "toiture",
      -  "salle-de-bain",
      -  "cuisine",
      -  "fenetres",
      -  "plomberie",
      -  "electricite",
      -  "ravalement-facade",
      -  "entretien-jardin",
      -  "menage-a-domicile",
      -  "climatisation",
      -  "volets-roulants",
      -  "porte-d-entree",
      -  "traitement-humidite",
      -  "monte-escalier",
      -  "douche-senior",
      -  "baignoire-a-porte"
      -]New value: +[
      +  "demenagement",
      +  "diagnostics-immobiliers",
      +  "peinture",
      +  "isolation",
      +  "pompe-a-chaleur",
      +  "chaudiere",
      +  "panneaux-solaires",
      +  "borne-de-recharge",
      +  "toiture",
      +  "salle-de-bain",
      +  "cuisine",
      +  "fenetres",
      +  "plomberie",
      +  "electricite",
      +  "ravalement-facade",
      +  "entretien-jardin",
      +  "menage-a-domicile",
      +  "climatisation",
      +  "volets-roulants",
      +  "porte-d-entree",
      +  "traitement-humidite",
      +  "monte-escalier",
      +  "douche-senior",
      +  "baignoire-a-porte",
      +  "entretien-pompe-a-chaleur"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / slug / enum
      Previous value: -[
      -  "demenagement",
      -  "diagnostics-immobiliers",
      -  "peinture",
      -  "isolation",
      -  "pompe-a-chaleur",
      -  "chaudiere",
      -  "panneaux-solaires",
      -  "toiture",
      -  "salle-de-bain",
      -  "cuisine",
      -  "fenetres",
      -  "plomberie",
      -  "electricite",
      -  "ravalement-facade",
      -  "entretien-jardin",
      -  "menage-a-domicile"
      -]New value: +[
      +  "demenagement",
      +  "diagnostics-immobiliers",
      +  "peinture",
      +  "isolation",
      +  "pompe-a-chaleur",
      +  "chaudiere",
      +  "panneaux-solaires",
      +  "borne-de-recharge",
      +  "toiture",
      +  "salle-de-bain",
      +  "cuisine",
      +  "fenetres",
      +  "plomberie",
      +  "electricite",
      +  "ravalement-facade",
      +  "entretien-jardin",
      +  "menage-a-domicile",
      +  "climatisation",
      +  "volets-roulants",
      +  "porte-d-entree",
      +  "traitement-humidite",
      +  "monte-escalier",
      +  "douche-senior",
      +  "baignoire-a-porte"
      +]
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so safety is covered. The description adds the genuinely useful behavioral fact that the response is a specification (steps and expected fields) rather than data, which an agent cannot infer from the annotations. It does not say what happens on an invalid slug, so it stops short of 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.

Conciseness3/5

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

The operative information is two short clauses, but they are buried behind a 25-item enumeration of service names that duplicates the enum in the input schema. Removing that catalogue would make the definition sharper without losing anything an agent needs.

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 one-parameter, read-only introspection tool with no output schema, the description covers what the tool is, what it returns in broad terms, and its place in the sequence before estimate_quote. Richer detail about the shape of the returned steps/fields would help an agent plan the follow-up call, but nothing essential is missing.

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 100% and the single parameter is a closed enum with 25 values plus a description ('Identifiant du devis'). The prose list of quote types in the description maps onto the same enum without adding format, defaults, or validation detail, so the schema does the real work.

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 states a specific resource and payload: it describes a Vitef quote estimate, returning 'étapes et champs attendus'. It also distinguishes itself from the sibling estimate_quote by being the preparatory lookup. The long parenthetical catalogue of 25 quote types restates the enum rather than sharpening the purpose, which keeps it from a 5.

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?

'À appeler avant estimate_quote' gives an explicit trigger and names the sibling it must precede, which is exactly the kind of routing an agent needs. There is no guidance on edge cases, such as what to do if the slug is unsupported or whether results can be cached across calls.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources