Skip to main content
Glama

HelpMyAgent

by io.github.helpmyagent
OverviewDiscussionsAdmin

French Property DPE

real_estate_fr_dpe

Finds ADEME energy-performance certificates for an address or French municipality. Use when: Find residential DPE records for a French address or municipality. Avoid when: An address can contain several dwellings and therefore several DPE records. Limitations: ADEME republishes data submitted by diagnosticians; an address match does not guarantee identification of the exact dwelling. Price: 0.010 USD per call via x402. Paid-call behavior: source records are not modified, but a successful invocation can consume the advertised x402 payment; the payment-required challenge is free, and repeating the tool after a completed paid invocation may require a new payment. Accepted x402 networks: eip155:8453, xrpl:0.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of records returned by this call. (minimum 1; maximum 50; default 10).
addressNoOptional value for “address” as defined by this API contract. (minimum length 5; maximum length 250).
code_inseeNoOptional value for “code insee” as defined by this API contract.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dpeYesStructured value returned for “dpe” as defined by this API contract.
locationYesStructured value returned for “location” as defined by this API contract.
truncatedYesWhether additional matching records existed beyond the returned result limit.
limitationsNoKnown interpretation, source-coverage or freshness limitations for this result.
total_countYesTotal number of matching records reported by the source or endpoint.
generated_atYesUTC timestamp at which this derived result was generated.
source_statusYesAvailability status of the relevant upstream public source. (allowed values: ok).
returned_countYesNumber of records included in this response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / required
      Previous value: -[
-  "location",
-  "source_status",
-  "total_count",
-  "returned_count",
-  "truncated",
-  "dpe",
-  "generated_at",
-  "limitations"
-]New value: +[
+  "location",
+  "source_status",
+  "total_count",
+  "returned_count",
+  "truncated",
+  "dpe",
+  "generated_at"
+]
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

The description discloses the ADEME republishing limitation, the non-modification of source records, and the critical paid-call behavior including that repeating a call may require a new payment. This goes well beyond the all-false annotations and gives the agent essential expectations.

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?

The purpose is front-loaded and each section (use/avoid, limitation, price, payment behavior, networks) earns its place. It is longer than the minimum, but the extra length is substantive rather than filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists, return values need no explanation. The description covers usage boundaries, a key data limitation, pricing, payment side effects, and accepted networks, making it fully actionable for a paid external API with no helpful annotations.

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%, with parameter descriptions already explaining limit, address, and code_insee constraints. The tool description adds only the high-level notion of address or municipality, which does not materially deepen parameter understanding.

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?

The description opens with a specific verb ('Finds') and a precise resource ('ADEME energy-performance certificates'), scoped to an address or French municipality. This clearly differentiates it from sibling real-estate tools like market, parcel, risks, transactions, and valuation.

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?

It provides explicit 'Use when' and 'Avoid when' conditions, including the important multi-dwelling caveat. However, it does not name an alternative tool to use when the address is ambiguous, so it falls just short of the highest bar.

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

All HelpMyAgent toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources