Skip to main content
Glama

GoTombola

Chiffres de la campagne

get_campaign_figures
Read-onlyIdempotent

Returns the aggregated sales figures of one shared campaign: tickets sold, amount collected, and a daily series over the requested number of days. The figures are totals only, with no detail per sale or per buyer.

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": {
      "code": "<code>"
    },
    "name": "get_campaign_figures"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesPublic campaign code, for example GABC123.
daysNoLength of the daily series, 1 to 90 days.

Output Schema

NameRequiredDescriptionDefault
as_ofYes
seriesYes
currencyYes
tickets_soldYes
amount_collectedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered. The description's one contribution beyond that is the aggregation-granularity caveat (totals only, no per-sale or per-buyer detail), which is genuinely useful output context, but it says nothing about freshness, currency, or behavior for a campaign with no sales.

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?

Two sentences, front-loaded with the return payload, with no filler or repetition. The second sentence is a compact scope qualifier that earns its place by clarifying granularity.

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?

With a full output schema, rich annotations and fully documented parameters, the description only needs to frame what the tool returns, which it does. Only minor gaps remain (currency, data freshness, empty-campaign behavior) that an agent could infer from the output schema.

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 coverage is 100% and both parameters are documented with a pattern example for code and a 1-90 range for days. The description's 'daily series over the requested number of days' merely restates the schema's own description of days, so it adds no meaning beyond structured data, warranting the baseline 3.

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 (returns) and resource (aggregated sales figures of one shared campaign) and enumerates the exact contents: tickets sold, amount collected, daily series. It does not explicitly distinguish itself from the sibling get_campaign_overview, so the boundary between 'figures' and 'overview' is left to inference.

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 implied rather than stated: an agent understands this fetches totals for a single campaign. The clause 'totals only, with no detail per sale or per buyer' functions as an implicit when-not (do not use this if you need line-item detail), but no alternative tool is named and no prerequisites for the campaign code are given.

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