Skip to main content
Glama

GoTombola

Prête au lancement ?

get_launch_readiness
Read-onlyIdempotent

Returns whether one shared campaign can be launched, the items still missing with their console links, and the status code of its authorisation.

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

Input Schema

NameRequiredDescriptionDefault
codeYesPublic campaign code, for example GABC123.
languageNoLanguage of the labels, French by default.

Output Schema

NameRequiredDescriptionDefault
readyYes
missingYes
authorisation_statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is fully covered by structured data. The description adds that a status code of the authorisation is included, but that detail is also carried by the output schema, so it adds modest value rather than new behavioral context such as caching or rate limits.

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, leading with the core answer (can it be launched). It loses a point for enumerating return fields that the output schema already documents, which is mild redundancy rather than padding.

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 an output schema, full parameter documentation and complete annotations, the description only needs to convey scope and intent, which it does. The remaining gap is the absence of any precondition or follow-up guidance, which matters for a readiness-check tool that likely gates a launch.

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 description coverage is 100%, including the campaign-code pattern and the language enum, so the input schema does the heavy lifting. The description only implies the single-campaign scope and never mentions the language parameter, adding little beyond the schema.

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?

A single specific verb-plus-resource statement: it returns launch readiness for one shared campaign, plus missing items with their console links and the authorisation status code. It is clearly not a figures or estimate tool, but it never names or contrasts with any sibling, so differentiation 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to call this rather than get_campaign_overview or estimate_campaign, no prerequisites (e.g. does the campaign need to be a draft?), and no statement about what to do with the result. Usage is only implied by the phrase 'launch readiness'.

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