Skip to main content
Glama

Modifier Sondage

modifier_sondage

Update an existing survey by changing only the fields you provide, such as title, location, description, options, draft status, or questions. Open surveys cannot be reverted to draft.

Instructions

Met à jour un sondage : seuls les champs fournis changent.

questions remplace la liste complète ; un sondage ouvert ne peut pas redevenir un brouillon.

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

Input Schema

NameRequiredDescriptionDefault
lieuNo
titreNo
optionsNo
brouillonNo
questionsNo
sondage_idYes
descriptionNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description bears the full behavioral burden. It does disclose two useful traits: partial updates (only supplied fields change) and that "questions" replaces the entire list, plus a state transition restriction. But it never says whether replacing questions discards existing responses, whether changes require ownership or permissions, or that this is an irreversible mutation for participants' answers.

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 with the partial-update rule front-loaded and zero filler. The second sentence is dense and unquoted field names slightly blur the distinction between field "questions" and generic wording, but it is efficient overall.

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 exists so return values need not be explained, but for a 7-parameter mutation with no annotations and 0% schema coverage, the description is far too thin. The destructive consequences of replacing questions and the semantics of most updatable fields are missing.

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 description coverage is 0% across 7 parameters, so the description must compensate and it only touches on two: "questions" (full replacement) and "brouillon" (state rule). titre, lieu, description and options are given no meaning at all, leaving the agent to guess their update semantics.

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?

States a specific verb and resource ("Met à jour un sondage") plus the partial-update semantic ("seuls les champs fournis changent"), which distinguishes it from a full-replace or create operation. It does not name any sibling (e.g. creer_sondage, dupliquer_sondage, modifier_reponse) to route the agent, so a 4 rather than a 5.

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 by the update verb and by the state constraint (an open survey cannot revert to draft), which tells the agent when the brouillon field is invalid. There is no explicit when-to-use vs. when-not guidance and no mention of alternatives such as creer_sondage or dupliquer_sondage for creating a modified copy.

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