Skip to main content
Glama

Rouvrir Sondage

rouvrir_sondage

Reopens a closed survey, applying a new closing date when provided or extending the deadline by one month by default.

Instructions

Rouvre un sondage clos ; nouvelle_cloture (« 2026-12-01 ») sinon +1 mois.

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

Input Schema

NameRequiredDescriptionDefault
sondage_idYes
nouvelle_clotureNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 behavioral burden, and it does disclose one important trait: the new closing date defaults to +1 month when omitted. It says nothing about permissions, whether existing responses are preserved or affected by reopening, or whether the reopening is reversible — gaps that matter for a mutation tool.

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?

A single front-loaded sentence with no filler: the action, the precondition, and the parameter default are all stated compactly. The telegraphic style (semicolon, "sinon +1 mois") costs nothing in clarity here.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Hmm — reassess: the tool has an output schema, so return values need no explanation, and the two parameters are covered by the description. The remaining gap is mutation side effects (permissions, effect on existing responses), which is real for a two-parameter state-changing tool, so a 3 is more accurate than a 5.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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, and it does: it gives the date format for nouvelle_cloture ("2026-12-01") and explains its default behavior (+1 mois), which the schema only shows as an empty string. sondage_id is left unexplained, though its meaning is evident from the name.

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 ("Rouvre") plus resource ("sondage") and a precondition ("clos"), which distinguishes it from clore_sondage and ouvrir_sondage without needing their schemas. It stops short of naming any sibling explicitly, so differentiation is inferred from the verb rather than stated.

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 word "clos" implies the applicable state of the poll, giving implicit when-to-use guidance. There is no explicit statement of when not to use it, no mention of what happens for a poll that is still open, and no reference to an alternative tool.

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