Skip to main content
Glama

Creer Sondage

creer_sondage

Create date or text polls for event scheduling and answer collection, with configurable settings, draft visibility, and automatic closing. No invitations are sent.

Instructions

Crée un sondage (aucune invitation envoyée).

options : réglages, ex. {"reply_access": "opened_to_everyone", "enable_anonymous_answer": 1, "hide_answers": 0}. brouillon=True : visible de moi seul. fermeture_auto : « 2026-12-01 » (sinon +1 mois côté serveur).

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": {
      "titre": "<titre>",
      "questions": "<questions>"
    },
    "name": "creer_sondage"
  }
}

Input Schema

NameRequiredDescriptionDefault
lieuNo
titreYes
optionsNo
brouillonNo
questionsYes
descriptionNo
fermeture_autoNo
fuseau_horaireNoEurope/Paris

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose genuinely non-obvious behavior: no invitations are sent, brouillon=True makes the poll visible only to the creator, and fermeture_auto defaults to +1 month server-side. It does not mention ownership/permission requirements, what happens on validation failure, or side effects for participants.

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 purpose is front-loaded and there is little filler, but the telegraphic fragments ('options : réglages, ex.', 'brouillon=True : visible de moi seul') read as notes rather than sentences, which costs some clarity. Nothing is redundant.

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 explained, and the description does cover the highest-risk behaviors (draft visibility, auto-close default, no invites). For an 8-parameter creation tool with zero annotations, however, the unexplained parameters and absence of any prerequisite or failure-mode context leave it only minimally complete.

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 must compensate. It adds real meaning for three parameters: example keys inside the free-form 'options' object, the visibility semantics of 'brouillon', and the accepted format/default of 'fermeture_auto'. However, titre, questions, lieu, description and fuseau_horaire get no explanation in the description, leaving roughly half the parameters underspecified.

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 a specific verb and resource ('Crée un sondage') and adds a meaningful scope note ('aucune invitation envoyée'). It does not distinguish itself from siblings such as dupliquer_sondage or modifier_sondage, but the creation intent is unambiguous.

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 explicit when-to-use guidance and no reference to alternatives like dupliquer_sondage or modifier_sondage. The parenthetical 'aucune invitation envoyée' hints at a workflow consequence but does not tell the agent when this tool is the right choice versus another.

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