Skip to main content
Glama

GoTombola

Aperçu de la campagne

get_campaign_overview
Read-onlyIdempotent

Returns the overview of one shared campaign by its public code: name, status, start and draw dates, ticket price, number of prizes, modules turned on, and the links to its public page and to its console.

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_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesPublic campaign code, for example GABC123.

Output Schema

NameRequiredDescriptionDefault
codeYesPublic campaign code, for example GABC123.
nameYes
statusYes
currencyYes
draw_dateYes
starts_onYes
modules_onYes
public_urlYes
console_urlYes
prize_countYes
ticket_priceYes

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 covered. The description adds genuine scope information by specifying that only 'shared' campaigns are addressable and by listing the returned facets, but it says nothing about behavior for unknown, unshared, or malformed codes.

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?

One front-loaded sentence with no filler; the verb and identifying key come first. The trailing enumeration slightly overlaps the existing output schema, but it is compact and helps at selection time, so nothing is seriously wasted.

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 single-parameter read tool with full schema coverage, complete annotations, and an output schema that documents return values, this is nearly complete. The only gaps are error/not-found behavior and any precondition that the campaign must be shared and accessible to the caller.

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%: the single 'code' parameter already carries the regex pattern and an example (GABC123). The description only restates 'by its public code', adding no format, case-sensitivity, or lookup-failure detail beyond the schema, so the baseline of 3 applies.

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 concrete verb and resource ('Returns the overview of one shared campaign by its public code') and enumerates the contents (name, status, dates, ticket price, prize count, modules, links), which is far more specific than the title 'Aperçu de la campagne'. It does not explicitly contrast with siblings such as get_campaign_figures or get_launch_readiness, so an agent still has to infer that 'overview' excludes metrics and readiness detail.

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: you call it when you have a campaign's public code and want a general snapshot. There is no explicit when-to-use, when-not, or pointer to alternatives like get_campaign_figures for statistics or list_my_campaigns for discovery, so routing among the campaign siblings is left to inference.

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