Skip to main content
Glama

DéclaClic : panneaux solaires

Vérifier une adresse pour des panneaux solaires

verifier_adresse_panneaux_solaires
Read-onlyIdempotent

Pour une maison en France métropolitaine où le particulier veut poser des panneaux solaires sur son toit : parcelle cadastrale, zone du PLU, protection patrimoniale (monument historique, site patrimonial), pièces de la déclaration préalable, délai d'instruction, et lien vers DéclaClic qui prépare le dossier à partir de cette adresse. Données publiques indicatives : redire au particulier ce qui est « à vérifier ».

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": {
      "adresse": "<adresse>"
    },
    "name": "verifier_adresse_panneaux_solaires"
  }
}

Input Schema

NameRequiredDescriptionDefault
adresseYesAdresse postale complète de la maison (numéro, rue, code postal, commune).

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 and open-world, so the safety profile is covered. The description adds behavior beyond that: the data are public and indicative, and the agent is told to foreground for the user what remains 'à vérifier' — a real presentation caveat not encoded anywhere else. It stops short of stating data sources' freshness limits or failure behavior for unmatched addresses.

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?

Scope is front-loaded in the opening clause, then the returned data are enumerated, then the 'indicative data' caveat closes it. It is a single dense sentence with no filler, though the mid-sentence list of six outputs makes it slightly run-on.

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 a one-parameter read-only tool with no output schema, the description usefully enumerates what comes back (cadastral parcel, PLU zone, heritage protections, required documents, instruction deadline, DéclaClic link), so an agent can decide whether to call it. What is missing is the sibling disambiguation and any note on how the response is organized.

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?

There is a single parameter with 100% schema description coverage, so the schema already defines the full postal address format. The description only adds the framing 'à partir de cette adresse', which gives no extra semantic detail (no normalization rules, no partial-address handling). Baseline 3 applies when the schema carries the burden.

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 names a concrete resource set the tool resolves for a given address: parcelle cadastrale, zone du PLU, protection patrimoniale, pièces de la déclaration préalable, délai d'instruction, plus a DéclaClic link. It also fixes the scope('maison en France métropolitaine', solar panels on the roof), so an agent knows exactly what the call produces. It never mentions or contrasts with the sibling demarche_panneaux_solaires_toiture, which is the one missing clarity element.

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?

Usage context is present and fairly specific: an individual homeowner in metropolitan France wanting rooftop solar panels. There is no explicit when-not guidance, no prerequisites about address quality beyond the schema, and no routing between this tool and the sibling, so the agent must infer the choice between checking an address and running the procedure.

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