Skip to main content
Glama

NLocale

Préparer le week-end dans l’Aisne

agenda_weekend
Read-onlyIdempotent

Rendez-vous publiés du vendredi au dimanche, calculés à la date actuelle de Paris. Sans secteur, reprend les fiches et l’ordre de la page https://nlocale.fr/ce-week-end/ quand une édition validée couvre ce week-end (selection_source, weekend_page) ; sinon sélection automatique. Secteur : Laon, Saint-Quentin, Soissons, Château-Thierry, Chauny, Hirson ou Villers-Cotterêts. Ne contient aucune promesse de maintien ni réservation.

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": "agenda_weekend"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNombre maximal de résultats, de 1 à 20. Défaut : 10 (20 pour agenda_weekend).
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
secteurNoUn des secteurs : Laon, Saint-Quentin, Soissons, Château-Thierry, Chauny, Hirson, Villers-Cotterêts. Sans secteur, l'outil reprend la page https://nlocale.fr/ce-week-end/ quand une édition validée couvre ce week-end.

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 declare readOnly, idempotent, non-destructive and closed-world, and the description adds real context beyond them: the weekend window is computed at the current Paris date, results may come from a validated editorial edition (selection_source, weekend_page) or from automatic selection, and there is no promise of events being maintained or bookable. That last caveat is useful behavioral framing the annotations cannot express.

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?

Four short sentences, front-loaded with the core result and date semantics, then the default selection rule, valid sectors, and the disclaimer. The URL and the parenthetical field names are dense but earn their place as selection-behavior detail.

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 listing tool with three fully documented optional parameters and no output schema, the description covers scope, default source, valid sectors, and the absence of booking guarantees. Only the explicit contrast with sibling search tools is missing.

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 parameter is already documented, and the description mostly restates the secteur default behavior rather than adding new meaning. It says nothing about limit or langue, leaving the schema to carry those.

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 states a concrete resource and scope: published events from Friday to Sunday, computed against the current Paris date. It is clearly distinguishable from search-oriented siblings like rechercher_evenements, though it never names an alternative explicitly.

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?

Guidance is limited to the no-sector default (reusing the ce-week-end page when a validated edition exists) and the list of valid sectors. It never says when an agent should pick this tool over chercher_sorties or rechercher_evenements, so the usage boundary is only implied by the name and weekend framing.

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