Skip to main content
Glama

Creneaux Compatibles

creneaux_compatibles
Read-only

Find conflict-free time slots for a survey poll by checking imported calendars and optional calendar names.

Instructions

Créneaux du sondage sans conflit dans les calendriers importés.

calendriers : noms ou identifiants à considérer (tous par défaut, y compris « @MyCal », l'agenda interne d'Evento).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sondage_id": "<sondage_id>"
    },
    "name": "creneaux_compatibles"
  }
}

Input Schema

NameRequiredDescriptionDefault
sondage_idYes
calendriersNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuinely useful behavioral context by stating that all calendars are considered by default, including Evento's internal "@MyCal" agenda — a scope detail not derivable from annotations. It says nothing about how conflicts are computed or about slot granularity.

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, front-loaded with the outcome and followed by the one parameter worth clarifying. No filler, though the parenthetical about @MyCal is slightly verbose.

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?

An output schema exists, so return values need not be described, and readOnlyHint covers safety. However, for a computation tool it remains ambiguous whether slots are computed over the poll's proposed dates or over raw calendar availability, and what counts as a conflict — an agent may misjudge the result.

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 0%, so the description carries the burden. It does explain the calendriers parameter well (names or identifiers, all by default, includes @MyCal), but sondage_id is left entirely unexplained, and the accepted identifier format is still vague.

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 resource ("Créneaux du sondage") with a clear qualifier ("sans conflit dans les calendriers importés"), which implicitly separates it from the sibling creneaux_incompatibles and conflits_sondage. It is clear what the tool returns, though it never explicitly names the contrasting tool.

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 statement of when to call this instead of creneaux_incompatibles or conflits_sondage, nor any precondition (e.g. that the poll must have responses or imported calendars). Usage is only inferable from the one-line purpose statement.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.