Skip to main content
Glama

Qualifications RGE d'un établissement (SIRET)

qualifications_rge
Read-onlyIdempotent

List the RGE (Reconnu Garant de l'Environnement) energy-renovation certifications of ONE French establishment, identified by its 14-digit SIRET, from the official ADEME list. Use it to check a contractor before work eligible for French renovation subsidies (MaPrimeRénov', CEE): each qualification comes with its domains, certifying body, start and end dates, and whether it is valid today; rge.qualifie is true when at least one is currently valid. When to use another tool: verifier_entreprise works on the whole company (SIREN) and only says whether an RGE label exists. Get the SIRET from rechercher_entreprise (siret) or verifier_entreprise (entreprise.siege.siret). Errors (never charged): an invalid SIRET is rejected before any payment request; an unknown or non-public establishment returns an error and is not settled. An establishment without any RGE certification returns qualifie: false and an empty list (this is a valid, charged answer). Payment: $0.01 per call via x402 (USDC on Base). No account or API key.

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": {
      "siret": "<siret>"
    },
    "name": "qualifications_rge"
  }
}

Input Schema

NameRequiredDescriptionDefault
siretYes14-digit SIRET of the establishment. Spaces, dots and dashes are accepted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / siret / description
      Previous value: -"SIRET, 14 chiffres."New value: +"14-digit SIRET of the establishment. Spaces, dots and dashes are accepted."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Although annotations already mark it read-only, idempotent, open-world, and non-destructive, the description adds substantial behavioral context: valid empty results are charged, invalid SIRETs are rejected before payment, unknown establishments error and are not settled, and payment is $0.01 via x402. It also explains return semantics such as `rge.qualifie` and the fields included.

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 description is front-loaded with purpose, scope, and sibling differentiation, then covers errors and payment. It is fairly long, but nearly every sentence provides actionable invocation or interpretation guidance, so the length is mostly justified.

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?

For a one-parameter read-only lookup without an output schema, the description supplies what an agent needs: SIRET source, result interpretation, empty-result behavior, error/payment semantics, and sibling alternatives. No material gaps remain.

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%, and the schema already documents the `siret` parameter in detail. The description still adds useful context by emphasizing the 14-digit SIRET and by naming upstream tools that provide it, but it does not add much beyond the schema for the parameter itself.

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 states a specific verb and resource: list RGE energy-renovation certifications for ONE French establishment identified by SIRET, sourced from the official ADEME list. It clearly distinguishes the unit of analysis (establishment/SIRET) from sibling tools that operate at company/SIREN level.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit use cases (checking a contractor before subsidy-eligible work), names the alternative verifier_entreprise and explains its limitation, and tells the agent where to obtain the SIRET via rechercher_entreprise or verifier_entreprise. The when-to-use and when-to-use-another-tool guidance is unusually complete.

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