Skip to main content
Glama

Conflits Sondage

conflits_sondage
Read-only

Detects conflicts between a survey's proposed dates and imported calendars by survey ID, helping you identify scheduling clashes before finalizing events.

Instructions

Conflits entre les propositions d'un sondage et les calendriers importés.

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

Input Schema

NameRequiredDescriptionDefault
sondage_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description needed to add what is actually computed or returned. It adds nothing beyond the topic — no indication of whether results are a list of conflicting slots, a count, or per-calendar breakdowns, nor of any prerequisites such as calendars having been imported first.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single fragment is short and wastes no words, but it is not front-loaded with an action and reads as a label rather than an instruction. Brevity here comes at the cost of specification rather than from efficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema covers return values, which lowers the burden, but for a tool whose purpose is a conflict report the definition still omits the operation, the parameter meaning, and any preconditions. It is not complete enough for an agent to select and invoke it confidently against the many sondage/calendrier siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for the single parameter sondage_id, so the description is the only source of meaning. It implies the tool operates on a poll but never states that sondage_id identifies which poll, nor what format the identifier takes.

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

Purpose3/5

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

The fragment names the domain precisely ('conflits entre les propositions d'un sondage et les calendriers importés'), which distinguishes it from siblings like creneaux_compatibles or lister_calendriers. However, there is no verb: it never says whether the tool lists, detects, or counts conflicts. An agent knows the topic but not the operation.

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 when-to-use guidance at all, and no mention of the closely related creneaux_compatibles / creneaux_incompatibles siblings that an agent would plausibly confuse it with. Usage must be inferred entirely from the topic fragment.

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