Skip to main content
Glama

NLocale

Rechercher guides, FAQ, méthode et offres NLocale

rechercher_contenus_publics
Read-onlyIdempotent

Contenus réellement publiés dans la langue demandée : guides de secteur et de commune, agenda, FAQ, méthode de Tata Nadège, présentation, offre aux collectivités, CGU et politique de confidentialité (extraits). Chaque résultat comprend une référence vers le détail public et son lien. Pagination : offset et pagination.next_offset.

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_contenus_publics"
  }
}

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.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, and the description still adds real context: results are limited to genuinely published content in the requested language, each hit carries a reference to the public detail plus its link, and pagination is offset-based with pagination.next_offset. It does not describe the full result shape or the total result count, but that is beyond what the annotations provide.

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 sentences, front-loaded with the content scope, followed by return-value and pagination notes. The content enumeration is long but each item earns its place by scoping the corpus. No filler or hedging.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a seven-parameter, output-schema-less search tool, the description covers result structure and pagination adequately, but leaves the agent without guidance on how the filters combine, what the result count looks like, or why this tool should be chosen over the four content-type siblings. Adequate, not complete.

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 each of the seven parameters is already documented in the schema, establishing a baseline of 3. The description only re-states pagination via offset and pagination.next_offset and the language-stickiness rule, which the schema already conveys for langue and query; it adds no new meaning about query matching, categorie or commune filtering.

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 description enumerates the resource scope precisely (sector and commune guides, agenda, FAQ, Tata Nadège method, presentation, offer to local authorities, CGU, privacy policy), which implicitly separates it from siblings that cover articles, establishments, events or places. It lacks an explicit verb and never names a sibling, so the distinction must be inferred from the content list rather than stated.

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 when-to-use or when-not-to-use guidance, and no alternative tool is named despite clear overlaps with rechercher_articles_carnet, rechercher_etablissements, rechercher_evenements and rechercher_lieux. The only usage-adjacent statement is that content is 'réellement publié dans la langue demandée', which is a scoping fact, not routing guidance.

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