Skip to main content
Glama

GoTombola

Préparer un brouillon de campagne

prepare_campaign_draft
Idempotent

Stores a draft of a new campaign (kind, name, country, dates, ticket price, prizes, description) for the signed-in organiser and returns the console link where the organiser reviews it and creates the campaign. The draft itself creates, launches and charges nothing, and it expires after 7 days. The same proposal_key with the same draft returns the same proposal.

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": {
      "proposal_key": "<proposal_key>",
      "draft": "<draft>"
    },
    "name": "prepare_campaign_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftYes
proposal_keyYesIdempotency key chosen by the client, 8 to 128 characters.

Output Schema

NameRequiredDescriptionDefault
summaryYes
expires_atYes
console_urlYes
proposal_idYes

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?

Annotations already flag readOnlyHint=false, destructiveHint=false and idempotentHint=true, but the description adds substantive traits the annotations cannot express: the draft creates, launches and charges nothing, and it expires after 7 days. It also spells out the exact idempotency contract ('The same proposal_key with the same draft returns the same proposal'), which is far more precise than the bare idempotentHint flag.

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?

Three sentences, each earning its place: purpose first, then the no-side-effects/expiry caveat, then the idempotency rule. Zero filler and the most decision-relevant constraint (nothing is created) is front-loaded in sentence two.

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 nested two-parameter mutation with an output schema already present, the description covers the safety profile, expiry window and idempotency contract, which is most of what an agent needs. It stops short of noting auth or rate-limit constraints and does not warn about what happens when the same proposal_key is reused with a different draft, a gap worth one point.

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?

With only 50% schema description coverage, the nested draft object is fully specified by the schema itself (enums, max lengths, date-time patterns, additionalProperties=false), so the schema does the heavy lifting. The description adds the draft's field list at a name-only level and supplies the only real semantic nuance — that proposal_key keys idempotency to the draft content — but contributes nothing about the nested draft's required versus optional fields.

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 ('stores a draft of a new campaign'), enumerates the fields carried, and clarifies the output ('returns the console link where the organiser reviews it and creates the campaign'). Sibling tools such as estimate_campaign or list_my_campaigns are never mentioned, so differentiation is left to inference, but the 'creates nothing' framing makes the scope unambiguous.

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?

The description implies a workflow — draft here, review and create in the console — and pins the audience ('the signed-in organiser'), which is useful context. It never says when to prefer this over estimate_campaign or get_launch_readiness, nor what to do if the organiser is unauthenticated, so guidance remains implicit rather than explicit.

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