Skip to main content
Glama

Supprimer Sondage

supprimer_sondage
Destructive

Permanently deletes a survey you own, removing it from Evento so it can no longer be accessed or managed.

Instructions

Supprime définitivement un sondage 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": "supprimer_sondage"
  }
}

Input Schema

NameRequiredDescriptionDefault
sondage_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, but the description adds genuinely new information: the deletion is permanent ('définitivement') and requires ownership. What it omits is the blast radius — whether associated responses, participants, or slots are also removed — and whether the operation fails for non-owners.

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

Conciseness5/5

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

One short sentence with the destructive qualifier and the ownership constraint front-loaded. Nothing is wasted and nothing is buried.

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 no explanation, and the permanence/ownership facts are covered. For a destructive one-parameter tool, though, the description should say what else gets deleted alongside the poll and how to identify the target poll.

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%, so the description must compensate for the undocumented sondage_id, and it does not. It never says whether the parameter is an identifier or a name, nor what format it takes, leaving the single required argument entirely unexplained.

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 ('Supprime définitivement') and resource ('un sondage'), and the adverb 'définitivement' distinguishes permanent deletion from reversible siblings like clore_sondage or rouvrir_sondage. It stops short of explicitly contrasting with those siblings, so it is clear but not fully differentiated.

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 ownership clause ('dont on est propriétaire') works as a precondition, which is useful selection guidance. However, it never states when to delete versus close (clore_sondage) or archive a poll, and no alternative is named.

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