Skip to main content
Glama

GoTombola

À faire

get_todo
Read-onlyIdempotent

Returns the to-do list of one shared campaign: each item with its phase, whether it blocks the campaign or is recommended, its label, and the console link where it is done.

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

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
as_ofYes
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds the item composition (phase, blocking/recommended, label, console link), but that overlaps with the declared output schema and adds nothing about auth, rate limits, or empty-list behavior.

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?

A single sentence with no filler; the resource and scope come first and the returned item fields follow as a compact enumeration. Nothing could be removed without losing content.

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 annotation coverage, and fully described parameters, the description only needs to establish purpose and scope, which it does. The remaining gap is routing guidance relative to the other campaign-inspection tools.

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% and both parameters are documented in-schema, including the code pattern example and the language enum defaulting to French. The description adds no meaning beyond that, so the baseline 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?

Names a specific verb and resource ("Returns the to-do list") and scopes it to "one shared campaign", then enumerates what each item carries: phase, blocking vs recommended status, label, and console link. That is concrete enough to distinguish it from the figures/overview siblings, though it never names an alternative.

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 this is the tool for campaign task/checklist status, but there is no explicit when-to-use, no exclusion of get_launch_readiness or get_campaign_overview, and no statement of prerequisites such as needing a campaign code first.

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