Skip to main content
Glama

GoTombola

Cadre légal d'une tombola

get_legal_frame
Read-onlyIdempotent

Returns the legal frame of a raffle in one country: the coverage level of our content (structured, indication or not_covered), the regimes that apply with who may organise, the kind of authority, the lead time and the documents, a one-sentence legal basis, and the official sources with the date they were checked. A country without content returns not_covered. Every answer carries a notice that it is a general indication, not legal advice.

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": {
      "country": "<country>"
    },
    "name": "get_legal_frame"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYesISO 3166-1 alpha-2 country code, for example FR.
languageNoLanguage of the notice.

Output Schema

NameRequiredDescriptionDefault
noticeYes
countryYes
regimesYes
sourcesYes
coverageYes
basis_sentenceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/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 genuinely new behavior: a country without content returns not_covered rather than erroring, and every answer appends a general-indication disclaimer. What is missing is any note on data freshness beyond 'the date they were checked' or on coverage granularity per country.

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?

Purpose is front-loaded in the opening clause, and the two follow-up sentences cover the empty-result case and the disclaimer efficiently. The middle list of return fields is dense and somewhat redundant given an output schema exists, but it is scannable and every element is substantive.

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 two-parameter, read-only lookup with a full output schema, the definition covers the essentials: what comes back at a high level, the not_covered edge case, and the mandatory disclaimer. Listing individual return fields duplicates the output schema somewhat, but the edge-case and disclaimer disclosures are the parts an agent actually needs before calling.

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% — the country pattern and example (FR) and the language enum are fully documented in the schema itself. The description only reinforces 'in one country' and that language governs the notice text; it adds no format, casing, or default guidance beyond that. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — 'Returns the legal frame of a raffle in one country' — then enumerates exactly what that frame contains (coverage level, regimes, authority, lead time, documents, legal basis, sources). This is unmistakably a legal-reference lookup, not a campaign-management operation like the sibling tools, so an agent can select it without opening the schema.

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: the country parameter and the 'not_covered' fallback make it clear this is a per-country lookup, but there is no explicit 'use this when…' framing and no routing to a related tool such as find_authority for authority-specific questions. The agent must infer the boundary conditions itself.

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