Skip to main content
Glama

Petit Papa Secret

Changer la marque ou le thème d'un tirage

modifier_marque
DestructiveIdempotent

Change, après le tirage, le nom du tirage, le nom affiché, le logo, les couleurs, la police, le message, la signature ou le thème. Les liens déjà envoyés restent les mêmes et montrent la nouvelle marque ; personne ne change de prénom tiré. Si un champ de marque est donné, la marque entière est remplacée : redonnez ceux à garder. Un logo vide le retire.

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

Input Schema

NameRequiredDescriptionDefault
fondNoCouleur de fond, #rrggbb.
logoNoAdresse https du logo.
themeNoThème graphique : classique, chalet, pull (pull moche) ou nuit (nuit étoilée).
titreNoNom du tirage, par exemple « Noël en famille 2026 ».
policeNoStyle de police.
couleurNoCouleur des boutons et des titres, #rrggbb.
messageNoTexte affiché à chaque participant.
signatureNoSignature du message, par exemple « Le CSE ».
organisateurYesLe lien organisateur rendu par creer_tirage (https://petitpapasecret.fr/o/...).
organisationNoNom affiché à la place de Petit Papa Secret (entreprise, association).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

With destructiveHint=true already declared, the description goes well beyond it: it explains WHY it is destructive (supplying any branding field replaces the entire branding, so the caller must re-supply fields to keep), that existing shared links keep working and display the new branding, that drawn names are unaffected, and that an empty logo removes it. This is exactly the call-safety context an agent needs.

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?

Three sentences, front-loaded with scope, followed by the two highest-value rules (link stability / replacement semantics). The opening field list partially duplicates the schema property descriptions and could be trimmed, but nothing is confusing or padded.

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 10-parameter destructive mutation with no output schema, the description covers the critical risks: replacement semantics, link persistence, and unaffected drawn names. It does not describe the response body, which is the main remaining gap given no output schema exists.

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 coverage is 100%, so baseline is 3; the description earns more by adding semantics the schema does not carry — the all-or-nothing replacement rule across branding fields and the empty-string-means-remove behavior for logo. The field enumeration itself largely repeats schema descriptions.

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 ("Change") on a specific resource with an explicit timing qualifier ("après le tirage") and enumerates the mutable fields (nom, logo, couleurs, police, message, signature, thème). An agent can distinguish this from creer_tirage, though no sibling is named explicitly.

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?

"après le tirage" implies this only applies to an already-created draw, which is useful context, but there is no explicit when-to-use versus when-not, and no alternative tool (e.g. creer_tirage for initial branding) is named. Guidance is implied rather than stated.

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