Skip to main content
Glama

GoTombola

Kit de partage

get_share_kit
Read-onlyIdempotent

Returns the sharing kit of one shared campaign: its short link and its tracked links, with their sale counts when available.

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

Input Schema

NameRequiredDescriptionDefault
codeYesPublic campaign code, for example GABC123.

Output Schema

NameRequiredDescriptionDefault
linksYes
qr_svgYes
short_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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. The description adds one genuine behavioral detail beyond that: sale counts are returned only 'when available', warning the agent that fields may be absent. It says nothing about what happens if the campaign exists but was never shared.

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 front-loaded sentence with the verb first, followed by the returned artifacts. No filler, no restatement of the title, and the caveat about sale counts is placed where it reads naturally.

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 only one required parameter and an output schema present, the description does not need to enumerate return shapes, yet it still summarizes them. The remaining gap is the absence of error or edge-case guidance for non-shared or unknown campaign codes.

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 coverage is 100% and the code parameter already carries a regex pattern and a worked example (GABC123), so the baseline is 3. The description contributes a little extra by framing the code as belonging to 'one shared campaign', reinforcing that the value must identify a shared campaign rather than any campaign.

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?

Specific verb (returns) plus resource (sharing kit of one shared campaign), and it names the concrete contents: short link, tracked links, sale counts. An agent can distinguish this from get_campaign_figures or get_campaign_overview by the resource being shared links rather than aggregate metrics, though no sibling is named explicitly.

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?

The phrase 'of one shared campaign' implies the tool applies only to campaigns that have been shared, which is useful context, but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative tool. The agent must infer that this is the retrieval step after sharing.

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