Skip to main content
Glama

NLocale

Rechercher des événements

rechercher_evenements
Read-onlyIdempotent

Événements publiés et actifs de l’agenda NLocale, avec leurs occurrences. Tri par défaut : à venir d’abord, par date, les rendez-vous datés avant les longues périodes d’ouverture. Pagination : offset et pagination.next_offset, avec le total. Chaque fiche donne ses sources, sa licence quand la source en publie une (Licence Ouverte 2.0 pour DATAtourisme) et ses dates. Les tarifs renseignés ne constituent pas un devis.

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

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.
gratuitNotrue seulement si la gratuité est explicitement connue.
periodeNoa_venir (défaut), archives ou tous.a_venir
date_finNoDate de fin inclusive, format AAAA-MM-JJ.
categorieNoCatégorie telle que publiée dans le catalogue, 120 caractères au plus.
date_debutNoDate de début inclusive, format AAAA-MM-JJ.
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

A3.7/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. The description still adds real context: the default ordering rule, the pagination contract (offset + pagination.next_offset with total), that each record carries sources, license, and dates, and the caveat that listed prices are not a quote.

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?

Front-loaded with the core scope, then sort, then pagination, then record contents — a sensible order with little waste. The DATAtourisme license parenthetical is the one clause that could be trimmed without loss.

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 an 11-parameter, no-required-parameter search tool with no output schema, the description does substantial work: it describes the result shape, the ordering, and the pagination contract. What remains thin is the relationship between the date filters and the periode enum, and any differentiation from siblings.

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 the schema already documents all 11 parameters including limits, formats, and enums; baseline is 3. The description reinforces only the offset/pagination semantics and adds nothing about query, langue, or the date-range interaction.

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 names a specific verb and resource ("Événements publiés et actifs de l'agenda NLocale, avec leurs occurrences") and defines the scope precisely. It does not differentiate against any sibling — neither chercher_sorties nor agenda_weekend nor rechercher_lieux is mentioned — so the agent must infer the boundary itself.

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

Usage Guidelines3/5

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

The description implies usage through its default sort (upcoming first) and pagination behavior, which helps an agent call it correctly. But it never states when to prefer this tool over agenda_weekend or chercher_sorties, nor any prerequise or exclusion, so routing guidance is left to inference.

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