Skip to main content
Glama

Dupliquer Sondage

dupliquer_sondage

Duplicate an existing poll into a new draft you own, so you can reuse its questions and settings without rebuilding it from scratch.

Instructions

Duplique un sondage en un nouveau brouillon (dont on est propriétaire).

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

Input Schema

NameRequiredDescriptionDefault
sondage_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose two useful traits beyond the name: the result is a draft (not a published/open poll) and the caller becomes its owner. It says nothing about whether the original is left untouched, what content is copied (questions, responses, participants), or what permission level is required to duplicate a poll one may not own.

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?

A single front-loaded sentence with zero filler; the ownership detail is parenthetically attached to the outcome. It is efficient, though the brevity contributes to the missing behavioral detail elsewhere.

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 here. However, for an unannotated mutation tool the definition should at least address permissions and what gets copied; those gaps keep it at minimum viable.

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% for the single parameter sondage_id, so the description must compensate. It implies the input identifies the source poll to copy, but does not clarify whether the id refers to a poll the caller owns, can access, or can be a draft itself.

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 names a specific verb ("Duplique") and resource ("un sondage") and states the concrete outcome: a new draft owned by the caller. This clearly separates it from creer_sondage or modifier_sondage without needing to name them, though no sibling is called out explicitly.

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 guidance on when to choose duplication over creer_sondage, nor any stated prerequisites such as needing read access to the source poll. The use case is only implied by the word "duplique".

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