Skip to main content
Glama

NLocale

Rechercher des établissements

rechercher_etablissements
Read-onlyIdempotent

Restaurants, hébergements et autres établissements publiés par NLocale. Filtrer par commune, code INSEE, catégorie et langue. Les dates de vérification et le statut décrivent les contrôles réellement effectués. Une fiche d'hébergement ne prouve pas une disponibilité.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rechercher_etablissements"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNombre maximal de résultats, de 1 à 20. Défaut : 10 (20 pour agenda_weekend).
queryNoMots recherchés, 160 caractères au plus. La recherche porte aussi sur les termes français de la même publication ; la réponse reste dans la langue demandée.
langueNoLangue de la réponse : fr, en, de, nl, it ou es. Défaut : fr. Une langue absente n'est pas remplacée par le français.fr
offsetNoDécalage de pagination. Défaut : 0. Le maximum est 500, sauf pour rechercher_articles_carnet (10000). La réponse donne pagination.total et pagination.next_offset.
communeNoNom de commune, 120 caractères au plus.
categorieNoCatégorie telle que publiée dans le catalogue, 120 caractères au plus.
insee_codeNoCode INSEE de commune, 5 caractères (chiffres ou lettres A-Z), par exemple 02408 pour Laon.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered structurally. The description adds genuinely useful semantic caveats — that verification dates and status reflect checks actually performed, and that a lodging record does not prove availability — which go beyond the annotations, though it says nothing about result volume or pagination behaviour.

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?

Three compact sentences with no filler, front-loaded with the resource envelope before the filter list and the trust caveats. Nothing is repeated verbatim, though the caveat sentences are dense and could be split for easier scanning.

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 read-only, fully documented 7-parameter search this is largely complete: scope, filters and data-trust caveats are all present. Since no output schema exists, a brief note on the response shape (the schema hints at pagination.total / next_offset) would have closed the remaining gap.

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?

Schema description coverage is 100%, so every one of the 7 parameters is already documented, including enum values, limits and defaults; baseline is therefore 3. The description repeats the filter axes (commune, INSEE code, catégorie, langue) without adding syntax, precedence or matching rules beyond what the schema states.

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 opening sentence names the resource concretely ("Restaurants, hébergements et autres établissements publiés par NLocale") and the second lists the filter axes, so an agent knows this is a filtered search over establishment listings rather than articles, events or generic places. It is clear, but differentiation from the closest sibling rechercher_lieux is left implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use / when-not-to-use guidance and no alternative sibling is named for overlapping cases (e.g. establishments vs lieux). The filtering sentence describes parameters rather than selection conditions, so the agent must infer routing from the resource noun alone.

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