Skip to main content
Glama

DPE Scraper & API: Energy Performance Certificates, Ratings

get_france_energy_ratings
Read-only

Fetches French home energy performance certificates (DPE) by city or postal code, returning energy/CO2 class, consumption, surface and estimated yearly bill.

Instructions

Energy performance certificates (DPE, ADEME open data) of homes in a French city or postal code: energy and CO2 class, surface, consumption, estimated yearly bill. Pay per result on your Apify account: run start $0.003, energy rating $0.001.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_france_energy_ratings"
  }
}

Input Schema

NameRequiredDescriptionDefault
ratingsNoKeep only these DPE classes. F and G are the "energy sieves" (passoires thermiques). Leave empty for all classes.
locationsNoFrench cities ("Grenoble"), postal codes ("38000") or INSEE codes. Paris, Lyon and Marseille cover all their arrondissements.
propertyTypeNoApartments, houses, or both.
maxRatingsPerLocationNoMost recent certificates first. Default here: 25.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely non-obvious behavior: the data source (ADEME open data) and the cost model ('pay per result... run start $0.003, energy rating $0.001'), which an agent needs to judge whether a broad query is affordable. It stops short of describing result limits or failure modes beyond the schema's maxRatingsPerLocation.

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

Conciseness5/5

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

Two sentences, front-loaded with what data is returned and followed by the pricing model. Every clause carries information — dataset, scope, output fields, and cost — with no filler or repetition of the title.

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 usefully compensates by listing the fields returned, and it covers the pricing dimension. It leaves minor gaps: no indication of result ordering/pagination behavior (only the schema's default of 25 hints at it) and no note on what happens when a location matches nothing.

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%, so all four parameters (ratings, locations, propertyType, maxRatingsPerLocation) are already documented with formats and defaults. The description only restates the geographic scope already in the schema and adds no new syntax, constraints, or interaction rules between parameters. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a concrete resource (energy performance certificates / DPE from ADEME open data) and its scope (homes in a French city or postal code), then enumerates the returned attributes: energy and CO2 class, surface, consumption, estimated yearly bill. None of the siblings (building permits, fuel prices, property sales) cover this dataset, so an agent can route to it unambiguously.

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 description implies usage ('homes in a French city or postal code') and the schema notes location formats, but there is no explicit statement of when to prefer this over a sibling tool or when not to use it. Guidance is inferable from the resource domain rather than stated.

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