Skip to main content
Glama

Creneaux Incompatibles

creneaux_incompatibles
Read-only

Identify time slots that conflict with imported calendars for a poll, with supporting events. Use it to detect scheduling conflicts before finalizing a survey.

Instructions

Créneaux en conflit avec les calendriers importés, événements à l'appui.

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

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.4/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this as a safe read. The description adds useful context beyond that—results come with supporting events, and the default scope is all imported calendars including the internal '@MyCal' agenda—but says nothing about scope limitations or how conflicts are determined.

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 statements, front-loaded with the outcome and followed by the parameter note. No filler, though the parameter sentence is embedded in prose rather than clearly labeled per argument.

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 annotations cover safety. Still, the unexplained required poll identifier and the absence of any explicit contrast with the compatible-slots sibling leave meaningful gaps for an agent choosing between them.

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 0%, so the description must carry the load. It explains calendriers well (names or identifiers, null default means all calendars including '@MyCal'), but the required sondage_id is left completely unexplained in both schema and description.

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 the specific resource: time slots in conflict with imported calendars, backed by events. It is distinct enough from the sibling creneaux_compatibles to be identifiable, though it never names that inverse tool 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?

Usage is implied rather than stated: you call it to find conflicting slots for a given poll, and the calendars argument defaults to everything. There is no explicit when-to-use versus creneaux_compatibles guidance or precondition statement.

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