Skip to main content
Glama

TrustyData

by app.trustydata

search_nearby

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
NameRequiredDescriptionDefault
latNo
lonNo
limitNo
offsetNo
addressNo
radius_mYes

TDQS

A4.8/5.0
Behavior5/5

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

Despite no annotations, the description fully discloses behavior: return fields (distance_m, enrichments like statistical_grid), pagination details (offset, total_estime, tronque flag, 5000 address cap), and address resolution. No contradictions.

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?

Exceptionally concise and well-structured. First sentence defines purpose, followed by logical groupings: center specification, output details, pagination instructions. Every sentence adds value with no redundancy.

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?

Covers return fields (distance_m, enrichments, resolved address), pagination behavior, and radius constraints. Lacks explicit error handling for invalid parameter combinations and doesn't mention the limit parameter. Overall, sufficient for a search tool but could be slightly more thorough.

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 has 0% description coverage, but the description explains key parameters: radius_m range, mutual exclusivity of address vs lat+lon, and offset for pagination. However, limit and default values are not explicitly described, leaving a minor gap.

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?

Clearly states the tool searches addresses from the official BAN repository within a radius, sorted by distance. Distinguishes from sibling tools like search_address and verify_address by specifying the proximity search and the resolution of free addresses.

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?

Provides explicit usage guidance: the central point must be either a free address or lat/lon pair, never both. Includes pagination advice (use offset=next_offset, reduce radius if truncated) and mentions the minimum plan requirement (Growth).

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool targets a distinct operation: search, verify, nearby lookup, company details, routing, matrix, etc. The descriptions explicitly cross-reference similar tools (e.g., 'préfère route_matrix' for bulk distances, 'préfère verify_address' for confirmation), making the boundaries clear.

Naming Consistency4/5

Most tools follow a consistent verb_noun pattern (search_address, get_company_details, verify_address). The exception is 'route_matrix', which is a noun phrase and breaks the pattern, though it remains readable and predictable enough.

Tool Count5/5

With 9 tools, the set is well-scoped within the ideal range. Each tool provides a meaningful capability without overlap or redundancy, covering address, company, routing, and locality data.

Completeness5/5

The server covers the core read-only workflows for its domain: address search/verification/nearby, company search/details, route calculation/matrix, and locality search/list. No obvious gaps or dead ends exist for a data lookup service.

Resources