Skip to main content
Glama

Petit Papa Secret

Lancer un tirage ouvert aux inscriptions

lancer_tirage

Ferme les inscriptions d'un tirage créé avec inscription vrai et tire au sort, 3 inscrits au moins. Chacun voit alors le prénom qu'il a tiré sur le lien reçu à son inscription ; aucun nouveau lien à envoyer.

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": {
      "organisateur": "<organisateur>"
    },
    "name": "lancer_tirage"
  }
}

Input Schema

NameRequiredDescriptionDefault
organisateurYesLe lien organisateur rendu par creer_tirage (https://petitpapasecret.fr/o/...).
confirmes_seulsNoVrai pour ne tirer que les personnes qui ont confirmé ; faux ou absent, tout le monde est tiré.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / confirmes_seuls
      Added value: +{
      +  "description": "Vrai pour ne tirer que les personnes qui ont confirmé ; faux ou absent, tout le monde est tiré.",
      +  "type": "boolean"
      +}
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations, it discloses important behavior: registrations are closed, the draw happens, and participants see the name they drew via their existing registration link without a new link being sent. It does not cover error behavior for fewer than three registrants or what happens if the operation is attempted twice, but the annotations already signal non-idempotence.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loads the main action and preconditions. Both sentences are informative and there is no unnecessary wording.

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

Completeness4/5

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

For a two-parameter mutation tool with no output schema, the description covers the main side effects, preconditions, and what participants see afterward. Some operational details, such as error handling or repeat invocation behavior, are left implicit.

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?

The input schema has 100% description coverage for both parameters, so the schema already explains organisateur and confirmes_seuls. The description does not add meaning about either parameter beyond the schema baseline.

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?

The description gives a specific action and resource: it closes registrations and performs the random draw for a tirage created with registration enabled. It clearly distinguishes this finalization step from creating a draw, though it does not explicitly name sibling tools or alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the key preconditions: the draw must have been created with registration enabled and must have at least three registrants. It gives clear context for when to use the tool, but does not explicitly describe when not to use it or name an alternative workflow.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources