Skip to main content
Glama

Meilleurs jours et heures

meilleurs_moments
Read-onlyIdempotent

Montre quand les clients viennent : moyenne de passages par jour de la semaine, répartition par heure, ou les créneaux (jour + heure) les plus chargés, sur une période au choix et à l’heure locale du commerce. Peut aussi compter les inscriptions de nouveaux clients. À utiliser pour « quel est mon meilleur jour ? », « à quelle heure ai-je le plus de monde ? », « quand lancer une offre pour remplir un creux ? ».

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

Input Schema

NameRequiredDescriptionDefault
auNoDernier jour inclus (AAAA-MM-JJ). Défaut : aujourd’hui.
duNoPremier jour inclus (AAAA-MM-JJ). Le donner suffit : la période devient « personnalisee ».
parNojour_semaine (défaut) : moyenne par lundi, mardi… ; heure : total par heure de la journée ; creneau : les couples jour + heure les plus chargés.jour_semaine
joursNoPour par=heure ou creneau : ne garder que ces jours de la semaine (ex. ["samedi"]).
limiteNoPour par=creneau : nombre de créneaux rendus (défaut 10).
mesureNopassages (défaut) ou nouveaux_clients (inscriptions à la carte).passages
periodeNoPériode étudiée, en jours du fuseau du commerce, aujourd’hui inclus pour les périodes en cours (ce_mois = du 1er à aujourd’hui). « personnalisee » utilise du/au. Défaut derniers_90_jours.derniers_90_jours

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior, so safety is covered. The description adds valuable operational context: results are in the shop's local time, periods are configurable, and current periods include today. It does not explain how averages are computed or whether zero-visit days are included, so not a 5.

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?

The description is compact and front-loaded: it opens with what the tool shows, then the aggregation modes, then the secondary measure, then usage examples. Every sentence carries information. Slightly dense with three example questions, but still efficient.

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?

With no output schema and seven optional parameters, the description explains what kinds of outputs to expect (weekday averages, hourly distribution, busiest slots) and the measures available. It omits detail on the result shape per mode, but for a read-only analytics tool it is largely sufficient for correct invocation.

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 coverage is 100%, so every parameter including the three enums is already documented in the schema. The description does not add syntax or format details beyond what the schema provides; it only restates the three aggregation modes at a high level. Baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific capability – showing when customers visit, broken down by weekday average, hour distribution, or busiest day+hour slots – and adds a secondary measure (new signups). The verb and resource are unambiguous, and it is clearly distinct from siblings like tableau_dashboard or rentabilite which deal with other analytics.

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

Usage Guidelines4/5

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

The tool includes three concrete example questions ('quel est mon meilleur jour ?', 'à quelle heure ai-je le plus de monde ?', 'quand lancer une offre pour remplir un creux ?') that anchor when to use it. It lacks explicit when-not-to-use guidance or named alternatives (e.g., contrast with tableau_de_bord), which keeps it from a 5.

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