Skip to main content
Glama

Aides à la rénovation énergétique (France)

Estimer les aides à la rénovation

estimer_aides_renovation
Read-onlyIdempotent

Estime MaPrimeRénov’ et les primes CEE pour des travaux dans un logement en France : montant par aide avec son calcul, plafonds de cumul appliqués, coût et reste à charge. Sans revenu ni catégorie, donne le résultat des quatre catégories de revenus. Ne couvre pas les aides locales.

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": {
      "travaux": "<travaux>"
    },
    "name": "estimer_aides_renovation"
  }
}

Input Schema

NameRequiredDescriptionDefault
dpeNoÉtiquette énergie du logement.
statutNoStatut d’occupation. Par défaut : propriétaire occupant.
travauxYesCodes des travaux envisagés. Plusieurs travaux d’isolation dans un logement classé E, F ou G relèvent de la rénovation d’ampleur.
logementNoType de logement. Par défaut : maison.
chauffageNoChauffage principal actuel : conditionne les bonifications CEE et la rénovation d’ampleur.
surface_m2NoSurface habitable en m².
code_postalNoCode postal du logement : fixe la zone climatique des primes CEE et les plafonds Île-de-France.
plus_de_15_ansNoLe logement a-t-il au moins 15 ans ? Par défaut : oui.
personnes_foyerNoNombre de personnes composant le foyer fiscal.
categorie_revenusNoCatégorie MaPrimeRénov’ si elle est connue. Sans catégorie ni revenu, le résultat donne les quatre catégories.
revenu_fiscal_referenceNoRevenu fiscal de référence du foyer, en euros. Utilisé pour ce seul calcul, jamais conservé.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnly/idempotent/non-destructive/closed-world, so safety is covered; the description adds real value by disclosing the return shape (montant par aide avec calcul, plafonds de cumul, coût, reste à charge) and the fallback to four income categories. This is useful behavioral context beyond the structured fields.

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?

Three tightly written sentences, front-loaded with purpose and output, then the no-income fallback, then the scope exclusion. No filler or repetition.

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 an 11-parameter estimation tool with no output schema, the description compensates by enumerating the return fields and the multi-category fallback, which is what an agent needs to interpret results. Given 100% schema coverage on inputs, little is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning about how omitting revenu/catégorie changes the result (four categories returned). That directly informs the categorie_revenus and revenu_fiscal_reference parameters beyond the schema text.

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?

States a specific verb (Estime) and resource (MaPrimeRénov’ et primes CEE) with scope (travaux dans un logement en France) and even the output contents. It does not explicitly contrast with siblings like trouver_categorie_revenus, but the 'Ne couvre pas les aides locales' boundary sharpens what it is not.

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?

The 'Sans revenu ni catégorie, donne le résultat des quatre catégories' note clarifies an optional-input case, and 'Ne couvre pas les aides locales' is a scope exclusion. However, it never names an alternative tool (e.g., trouver_categorie_revenus) to consult first, so usage guidance is implied rather than explicit.

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