Skip to main content
Glama

Reponses Participant

reponses_participant
Read-only

Retrieve a participant's detailed survey responses by survey and participant ID, helping poll owners inspect submitted answers.

Instructions

Détail des réponses d'un participant (propriétaire du sondage).

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>",
      "participant_id": "<participant_id>"
    },
    "name": "reponses_participant"
  }
}

Input Schema

NameRequiredDescriptionDefault
sondage_idYes
participant_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

readOnlyHint=true already establishes that this is a safe read, and an output schema exists, so the description's remaining burden is small. Still, the only hint it offers is the ambiguous "(propriétaire du sondage)", which never states whether the caller must own the poll, what happens when the participant doesn't belong to the poll, or whether results are paginated.

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 no filler and the resource stated up front. It is concise, though partly because it omits necessary detail rather than because it is well edited.

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

Completeness2/5

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

The tool is a simple read and has an output schema, which lowers the bar, but with two undocumented required parameters and no routing guidance among many response-related siblings the definition leaves real gaps. An agent cannot reliably determine how to supply participant_id or why this differs from reponses_question.

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%, so the description must compensate, but it never explains sondage_id or participant_id — neither format nor how to obtain a participant_id (presumably from lister_participants). The parenthetical only faintly implies a coupling between the two identifiers.

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 phrase "Détail des réponses d'un participant" identifies the resource (a participant's answers) but has no explicit verb and does not distinguish it from close siblings such as reponses_question or resultats_sondage. The parenthetical "(propriétaire du sondage)" adds ambiguity rather than clarifying scope, since it could describe an access restriction or the participant's role.

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?

The description gives no indication of when to call this instead of reponses_question, resultats_sondage, or lister_participants, and states no prerequisites. An agent must guess which of the several response-reading siblings to pick.

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