Skip to main content
Glama

Ouvrir Sondage

ouvrir_sondage

Opens a poll in the browser so users can submit responses manually or share it for others to participate.

Instructions

Ouvre un sondage dans le navigateur (réponse manuelle, partage).

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": "ouvrir_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.4/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 burden; it does disclose the key behavioral trait that a browser is launched, which is more than most definitions offer. It says nothing about prerequisites (must the survey be open/active?), permissions, whether server state changes, or failure modes, leaving meaningful gaps for a side-effecting tool.

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 no redundant phrasing; the only inefficiency is the vague parenthetical, which spends words without resolving anything.

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?

Complexity is low and an output schema exists, so return values need not be explained. Still, for a tool whose main effect is an external browser launch, the definition omits prerequisites and state requirements, leaving an agent unsure when the call will succeed.

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

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single parameter sondage_id is undocumented in both schema and description. The identifier name is largely self-explanatory, so an agent can probably supply it, but the description contributes no additional meaning such as format, source of the ID, or behavior when it is unknown.

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 ('Ouvre un sondage') plus the medium ('dans le navigateur'), which distinguishes it from obtenir_sondage and rouvrir_sondage by signalling a browser-launch side effect. The parenthetical '(réponse manuelle, partage)' is cryptic and adds ambiguity rather than precision about what opening actually accomplishes.

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?

Usage is only implied: the agent must infer that this is for cases where a human will answer manually or share the survey in a browser. No explicit when-to-use, when-not-to-use, or named alternative (e.g. repondre_sondage for programmatic answers) is given.

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