Skip to main content
Glama

Clore Sondage

clore_sondage

Close a survey and notify participants and guests by email about the closure. Use it to finalize polls and keep all invitees informed.

Instructions

Clôt un sondage (Evento prévient participants et invités par 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>"
    },
    "name": "clore_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, the description carries the full load: it usefully discloses a side effect beyond the schema, namely that Evento emails participants and guests. It does not say whether closing is reversible (a rouvrir_sondage sibling exists), what happens to responses or pending invitations, or what permissions are required.

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?

One short sentence with the action front-loaded and the side effect in parentheses; no filler. It is efficient, though terse to the point that no usage or parameter detail survives.

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 and tool complexity is low (one required parameter), so return values need not be explained. However, for a state-changing operation with email side effects, the definition omits reversibility and the effect on existing responses, leaving a meaningful gap.

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% for the single parameter, and the description never mentions sondage_id or what identifier it expects. The agent can only infer that it is the poll to close; the description does not compensate for the coverage gap.

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 ('Clôt un sondage'), which clearly separates it from ouvrir_sondage, rouvrir_sondage and supprimer_sondage by implication. It does not explicitly name any sibling to contrast against, so it stops short of 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?

No explicit when-to-use or when-not-to-use guidance and no named alternative (e.g., closing vs. deleting vs. reopening a poll). Usage is only implied by the verb 'clôt' plus the note that closing triggers outgoing email, which signals it is a consequential end-state action.

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