Skip to main content
Glama

GoTombola

Estimation d'une campagne

estimate_campaign
Read-onlyIdempotent

Estimates the money of a campaign from its ticket price and the number of tickets expected: gross amount, plan fee, Flex fee beyond the plan caps, payment provider fee, net amount after the value of the prizes, and the cheapest plan. Amounts are integers in minor units (cents) of the pricing currency. The result is an estimate, dated by the prices it uses.

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": {
      "ticket_price_minor": "<ticket_price_minor>",
      "tickets_expected": "<tickets_expected>"
    },
    "name": "estimate_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
planNo
languageNo
providerNo
tickets_expectedYes
tickets_per_saleNo
prizes_value_minorNo
ticket_price_minorYes

Output Schema

NameRequiredDescriptionDefault
netYes
feesYes
grossYes
inputsYes
noticeYes
prices_datedYes
plan_suggestedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description adds value on top: it states amounts are integers in minor units (cents) of the pricing currency and warns the result is an estimate 'dated by the prices it uses', signalling the output is price-snapshot dependent. It does not state what happens when optional inputs are omitted, which is the main remaining behavioral gap.

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?

Two sentences, both load-bearing: the first front-loads the core computation and enumerates the returned components, the second establishes units and the estimate caveat. No filler, no repetition of the name or title.

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 agent can call it with the two required parameters, and the existing output schema relieves the description of explaining return values. However, for a 7-parameter tool with zero schema coverage, the omitted optional parameters (tickets_per_sale, language) and any defaulting behavior for plan/provider are not covered, leaving the caller to guess at non-trivial inputs.

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 description coverage is 0% with 7 parameters, so the description must compensate, and it largely does: it names ticket_price_minor and tickets_expected as the driving inputs and implies plan, provider, and prizes_value_minor through the fee and net-amount components it lists. It adds the crucial units convention (minor units of the pricing currency) absent from the schema, but leaves tickets_per_sale and language entirely unaddressed.

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 opens with a specific verb and resource: estimating a campaign's money from ticket price and tickets expected, then enumerates the exact components produced (gross, plan fee, Flex fee over plan caps, provider fee, net after prizes, cheapest plan). That makes it clearly a what-if financial projection rather than a data retrieval, implicitly separating it from get_campaign_figures / get_campaign_overview, though no sibling is named.

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: an agent can infer it should call this to project campaign finances before a launch, but there is no explicit when-to-use, when-not-to-use, or 'use X instead when you want actual recorded figures' statement. With siblings like get_campaign_figures available, an explicit contrast would have earned a higher score.

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