Skip to main content
Glama

Resultats Sondage

resultats_sondage
Read-only

Retrieve poll results as an email digest, Evento-compatible CSV, or raw JSON by supplying a survey ID.

Instructions

Résultats d'un sondage : digest pour courriel, CSV Evento ou JSON brut.

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

Input Schema

NameRequiredDescriptionDefault
formatNoresume
sondage_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this is a safe read, and the description is consistent with it. The added value is semantic mapping of each format ('digest pour courriel', 'CSV Evento', 'JSON brut'), which tells the agent what kind of payload it will get. It does not mention volume limits, permission requirements, or whether the digest differs in content from the raw export.

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 short sentence with zero filler, front-loading the resource and enumerating the format options. It is arguably over-compressed for a tool with two parameters, but nothing is wasted.

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 structure need not be explained, and the read-only nature is covered by annotations. What is missing is operational context an agent would want before calling: whether results are available at any poll state, and whether the CSV/digest forms differ in scope from the raw JSON.

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 description coverage is 0%, so the description carries the burden, and it does explain what the three enum values of 'format' actually produce, which the schema alone cannot. The 'sondage_id' parameter is left entirely implicit, but its meaning is self-evident from the tool name and required-parameter listing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (poll results) and the three output formats, which makes the tool's output distinguishable from plain poll retrieval. However, it is a noun phrase with no verb ('retrieve', 'export') and never contrasts itself with results-adjacent siblings such as reponses_question or reponses_participant, so the agent must infer what makes this tool distinct.

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?

No when-to-use or when-not-to-use guidance is given; the agent is not told whether this requires a closed poll, whether it works while voting is open, or when to prefer it over other response-reading tools. The only implicit guidance is the format hint, which selects an output shape rather than a scenario.

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