Skip to main content
Glama

TrustyData

by app.trustydata
OverviewDiscussionsAdmin

Vérifier et normaliser une adresse

verify_address
Read-onlyIdempotent

Vérifie et normalise une adresse française contre le référentiel géographique officiel (BAN). Renvoie un verdict (match_exact, match_probable, aucun_match) et l'adresse canonique, déjà découpée en trois lignes postales prêtes à écrire (ligne_voie, ligne_complement, ligne_commune) — à utiliser telles quelles plutôt que de recomposer l'adresse. Selon le plan : coordonnées GPS + Lambert 93 (Starter+), code IRIS (Growth+), statistiques INSEE Filosofi du carreau 200 m dans statistical_grid : population, répartition par tranches d'âge (0-3 à 80+), ménages, pauvreté, niveau de vie, époque de construction des logements (Business). Plan minimum : Discovery. Une adresse par appel.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesAdresse postale française en texte libre, telle que saisie (fautes, abréviations et accents manquants tolérés).
detailsNoInclure les blocs détaillés (position GPS et Lambert 93, IRIS, grille statistique — selon le plan). Défaut vrai.
max_resultsNoNombre maximal de candidats renvoyés (défaut 5).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / address / description
      Added value: +"Adresse postale française en texte libre, telle que saisie (fautes, abréviations et accents manquants tolérés)."
    • addedInput schema / properties / details / description
      Added value: +"Inclure les blocs détaillés (position GPS et Lambert 93, IRIS, grille statistique — selon le plan). Défaut vrai."
    • addedInput schema / properties / max_results / description
      Added value: +"Nombre maximal de candidats renvoyés (défaut 5)."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, and the description adds meaningful behavior: the verdict taxonomy, canonical line labels, plan-dependent enrichment (GPS/Lambert 93, IRIS, Filosofi statistical_grid), and the one-address-per-call constraint. No statement contradicts the annotations.

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 main purpose is front-loaded in the first sentence, followed by output behavior, plan-tier extras, and the per-call limit. The plan-tier enumeration is somewhat long but earns its place by telling the agent exactly what to expect from `details`. The structure is logical, though not as tight as a two-sentence definition.

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?

Given rich annotations, full schema coverage, and a present output schema, the description supplies the key missing context: BAN verification, verdict behavior, postal-line outputs, plan-based variance, and the single-address constraint. It does not explicitly contrast with overlapping siblings like get_address_details or search_address, but its distinctive vocabulary makes correct selection likely.

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?

Parameter descriptions in the schema already cover 100% of the three parameters, so the baseline is 3. The description goes slightly beyond by imposing 'Une adresse par appel' and by tying the `details` parameter to plan-dependent blocks such as statistical_grid. It doesn't re-document parameters, but adds the operational constraints that matter.

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 'Vérifie et normalise une adresse française contre le référentiel géographique officiel (BAN)', a precise verb-resource-target statement. It distinguishes itself from siblings by naming verdict types (match_exact, match_probable, aucun_match) and a canonical three-line postal output. 'Une adresse par appel' further clarifies its single-item verification scope.

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 clearly describes the use case: verifying/normalizing one French address against the official BAN and returning ready-to-use postal lines. The instruction to use ligne_voie/ligne_complement/ligne_commune as-is rather than recomposing the address is practical guidance. It doesn't name alternatives or exclusions, but the context is sufficient to differentiate from search/detail siblings.

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

All TrustyData 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