TrustyData

Adresses à proximité d'un point

search_nearby

Read-onlyIdempotent

Recherche les adresses du référentiel officiel (BAN) situées dans un rayon de radius_m mètres (1 à 50 000) autour d'un point central, triées par distance croissante. Le point central est SOIT une adresse libre (address), SOIT un couple lat+lon WGS84 — jamais les deux. Une adresse libre est résolue comme verify_address et renvoyée dans point_central.adresse_resolue. Chaque résultat porte distance_m (mètres, à vol d'oiseau) et les enrichissements du plan (mêmes paliers que verify_address, dont statistical_grid Filosofi en Business). Pagination : passer offset=pagination.next_offset pour charger la page suivante (null = fin de parcours) ; pagination.total_estime est une estimation ; si pagination.tronque vaut true, le cap de 5000 adresses est atteint — réduire le rayon pour l'exhaustivité. Plan minimum : Growth.

Input Schema

TableJSON Schema

Name	Required	Description
`lat`	No	Latitude WGS84 du centre, avec `lon` et sans `address`.
`lon`	No	Longitude WGS84 du centre, avec `lat` et sans `address`.
`limit`	No	Nombre de résultats par page (défaut 10, plafond 50).
`offset`	No	Décalage de pagination : reprendre à `pagination.next_offset` de la réponse précédente.
`address`	No	Centre par adresse libre (un nom de commune suffit). Exclusif de `lat`/`lon`.
`radius_m`	Yes	Rayon de recherche en mètres autour du centre.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedSep 14, 2026

addedInput schema / properties / address / description

Added value: +"Centre par adresse libre (un nom de commune suffit). Exclusif de `lat`/`lon`."

addedInput schema / properties / lat / description

Added value: +"Latitude WGS84 du centre, avec `lon` et sans `address`."

addedInput schema / properties / limit / description

Added value: +"Nombre de résultats par page (défaut 10, plafond 50)."

addedInput schema / properties / lon / description

Added value: +"Longitude WGS84 du centre, avec `lat` et sans `address`."

addedInput schema / properties / offset / description

Added value: +"Décalage de pagination : reprendre à `pagination.next_offset` de la réponse précédente."

addedInput schema / properties / radius_m / description

Added value: +"Rayon de recherche en mètres autour du centre."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

First observedJul 13, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already mark the tool as read-only, idempotent, open-world, and non-destructive, but the description adds substantial behavioral detail: addresses are resolved like verify_address, results carry distance_m, enrichments follow plan tiers including statistical_grid Filosofi, pagination semantics are explained (next_offset, total_estime, tronque), and a 5000-result cap is disclosed. This goes well beyond 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description opens with the core purpose in the first sentence, then efficiently covers center modes, result contents, pagination, truncation, and plan requirements. Every sentence contributes distinct information and none is redundant with the schema or annotations.

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 6-parameter spatial search with pagination, center-mode exclusivity, a 5000-address cap, and plan restrictions, the description is complete. An output schema exists, so the description does not need to enumerate return fields, but it still explains the crucial output concepts like distance ordering, resolved address, and truncated pagination.

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 each parameter already has a meaningful schema description, so the baseline is 3. The description adds further value by explaining radius units and range (1–50,000 m), reinforcing address/lat+lon exclusivity, describing how address resolution appears in point_central.adresse_resolue, and clarifying the pagination contract for offset. This is more than the schema alone provides.

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 names a specific verb and resource: searching BAN addresses within a radius around a center point, sorted by distance. It clearly distinguishes the tool's spatial-search scope from siblings like search_address or verify_address by emphasizing the radial proximity and center-point modes.

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?

The description clearly explains when to use this tool: to find addresses within a radius of a center, with explicit constraints on center modes and pagination. It does not explicitly name alternative tools or state 'use X instead', but the context is unambiguous and includes practical guidance such as reducing the radius when truncation occurs.

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

All TrustyData tools Inspect

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.