Skip to main content
Glama

TrustyData

by app.trustydata
OverviewDiscussionsAdmin

Rechercher des adresses

search_address
Read-onlyIdempotent

Recherche des adresses françaises à partir d'un texte libre (même partiel) et renvoie des candidats classés par pertinence (score 0-1). Pour confirmer UNE adresse précise, préfère verify_address. Chaque candidat porte les trois lignes postales prêtes à écrire (ligne_voie, ligne_complement, ligne_commune). Enrichissements selon le plan (mêmes paliers que verify_address, dont statistical_grid Filosofi en Business). Plan minimum : Discovery.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNombre maximal de résultats (défaut 10).
queryYesDébut d'adresse ou adresse partielle à compléter (numéro, voie, commune…).
detailsNoInclure les blocs détaillés (position GPS et Lambert 93, IRIS, grille statistique — selon le plan). Défaut vrai.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • 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 / limit / description
      Added value: +"Nombre maximal de résultats (défaut 10)."
    • addedInput schema / properties / query / description
      Added value: +"Début d'adresse ou adresse partielle à compléter (numéro, voie, commune…)."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, and idempotent hints, so the safety profile is covered. The description adds valuable behavioral details: ranking by relevance, the structure of returned candidates (three postal lines), and enrichment tiers tied to the plan. This goes beyond annotations without contradicting them.

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?

Four concise sentences, each carrying essential information. The main purpose is first, then routing to the sibling, then output details, then plan requirements. No filler, well-front-loaded.

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 and annotations cover the safety profile, the description is complete. It explains the ranking, the candidate structure, and enrichment levels, and even notes the minimum plan. An agent has everything needed to call this tool correctly and understand its results.

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%, so the baseline is 3. The description adds context by explaining that the query accepts partial text and that candidates include postal lines, which enriches the meaning of the parameters. It doesn't rehash every schema field but adds enough to clarify usage beyond the bare schema.

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 action (search French addresses from free text), a clear scope (French addresses, partial text), and the output (ranked candidates with a relevance score). It also distinguishes itself from verify_address by naming the sibling explicitly, making it unambiguous.

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?

The description explicitly recommends verify_address for confirming a single precise address, clearly routing the agent when to use this tool vs. the alternative. It also mentions the minimum plan required (Discovery), giving actionable selection criteria.

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