Skip to main content
Glama

NLocale

Chercher des sorties sourcées

chercher_sorties
Read-onlyIdempotent

Alias stable de rechercher_evenements : commune, dates, catégorie, gratuité explicitement connue et langue. Les résultats comprennent les références des fiches publiques et leurs sources.

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

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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one substantive behavioral fact beyond that — results include references to public fiches and their sources — plus a note that gratuité is only applied when explicitly known. It says nothing about pagination behavior or result ordering.

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?

Two short sentences with no filler, and the identity/alias statement is front-loaded before the facet list. The second sentence about result contents is well-placed, though the facet enumeration duplicates schema material.

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 an 11-parameter, all-optional search tool with full schema coverage and no output schema, the description covers what it returns (fiche references and sources) but omits pagination/limit behavior and any guidance on combining filters. Adequate but with clear gaps for a tool of this parameter richness.

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 all 11 parameters are documented in the schema itself. The description only restates a subset (commune, dates, catégorie, gratuité, langue) without adding format, defaulting, or interaction semantics, so the baseline of 3 applies.

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 identifies the tool as a stable alias of rechercher_evenements and enumerates the searchable facets (commune, dates, catégorie, gratuité, langue), so an agent can infer it searches event listings. It stops short of a direct verb+resource statement ('search events'), relying on the sibling name to convey the action, but the resource and scope are nonetheless recognizable.

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?

It declares itself an alias of rechercher_evenements but never says when to prefer this tool over that sibling, nor when not to use it. No prerequisites, exclusions, or selection criteria are given, leaving the agent to guess why two apparently equivalent tools exist.

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