Skip to main content
Glama

Estimer un devis

estimate_quote
Read-onlyIdempotent

Donne une fourchette de prix TTC pour des travaux, un déménagement, des diagnostics ou d’autres prestations, selon les champs de get_quote. La personne peut ensuite recevoir de vrais devis sur la page renvoyée.

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": "estimate_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesIdentifiant du devis.
valuesNoValeurs des champs, par clé (voir get_calculator ou get_quote). Les champs absents prennent leur valeur par défaut.

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.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds real value beyond them: the result is a price range including tax (TTC) and the returned page lets the person obtain actual quotes, clarifying the output's nature and downstream use.

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?

Two sentences, front-loaded with the core action and output, with no filler. The second sentence adds useful downstream context rather than padding.

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?

With no output schema, the description carries the burden of explaining the return, and it does so adequately (TTC price range plus a page for real quotes). The nested values object is only loosely explained, but the schema covers its structure.

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 coverage is 100%, so the schema already documents slug and values. The description adds only a pointer that field keys come from get_quote, which is marginal but consistent with the schema's own note. Baseline 3 applies.

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 verb and output ('Donne une fourchette de prix TTC') for a concrete resource (travaux, déménagement, diagnostics). It implicitly separates itself from get_quote by framing this as an estimate that precedes real quotes, though it never names the sibling explicitly.

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?

It hints at the workflow ('selon les champs de get_quote', then real quotes on the returned page), which implies this is a pre-quote estimation step. However, there is no explicit when-to-use/when-not guidance or direct comparison to get_quote or compute_calculator.

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