Skip to main content
Glama

Modifier Reponse

modifier_reponse

Updates previously submitted survey responses using a participant token or email, letting respondents correct answers and comments without resubmitting from scratch.

Instructions

Modifie des réponses déjà envoyées (jeton de participant ou courriel).

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>",
      "reponses": "<reponses>"
    },
    "name": "modifier_reponse"
  }
}

Input Schema

NameRequiredDescriptionDefault
courrielNo
reponsesYes
sondage_idYes
jeton_participantNo

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 carries the full behavioral burden. It states that existing responses are modified and how the participant is identified, but omits permissions, whether closed polls can be edited, whether changes replace or merge existing answers, and error behavior.

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?

The description is a single front-loaded sentence with no wasted wording. It is appropriately compact, though its brevity contributes to the gaps in behavioral and parameter guidance.

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?

For a mutation tool with four parameters, no annotations, and only a minimal description, this is under-specified. The output schema means return values need not be described, but an agent still lacks enough context about edit constraints and parameter usage.

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 for top-level parameters is 0%, so the description should compensate. It clarifies that jeton_participant and courriel are identification alternatives, but does not explain sondage_id or the required reponses structure, leaving the core input semantics to the schema.

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 uses a specific verb and resource: 'Modifie des réponses déjà envoyées', and clarifies that participants can be identified by token or email. It is distinguishable from creating answers, though it does not explicitly name a sibling tool.

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?

The phrase 'déjà envoyées' implies this is for updating existing responses rather than submitting new ones, giving useful implied guidance. However, it does not state when not to use it, prerequisites, or explicitly compare it to alternatives like repondre_sondage.

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