Skip to main content
Glama

Reponses Question

reponses_question
Read-only

Retrieve every answer to a survey question using its question ID, returning the owner's responses or your own when you are not the owner.

Instructions

Toutes les réponses à une question (propriétaire), ou la sienne sinon.

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": {
      "question_id": "<question_id>"
    },
    "name": "reponses_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
question_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations only declare readOnlyHint=true, so the description's disclosure that owners see all responses while others see only their own is genuine added behavioral value about result scoping. It stops short of covering ordering, pagination, or what happens when the question does not exist or access is denied.

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, front-loaded sentence with no filler; the scoping condition is placed immediately after the primary statement. It is terse to the point of under-specification, 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-value detail is not required, and the permission-scoping note covers the main behavioral risk. However, for a lookup tool keyed on an undocumented ID with a visibility branch, the definition leaves the agent without enough to call confidently in edge cases.

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 question_id, so the description carries the burden of explaining it and does not — no format, identifier source, or validity rules are given beyond the generic word 'question'. The parameter name is self-evident, which limits the damage, but the compensation gap is real.

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 ('toutes les réponses à une question') but supplies no verb and no explicit contrast with the closest sibling, reponses_participant. An agent can infer it retrieves answers for a given question, but must guess how it differs from the participant-scoped variant.

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 clause 'ou la sienne sinon' hints at a permission-based fallback (owner vs. non-owner), which is useful context, but there is no guidance on when to pick this over resultats_sondage, reponses_participant, or obtenir_sondage. No exclusions or prerequisites are stated.

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