Skip to main content
Glama

GoTombola

Autorité compétente

find_authority
Read-onlyIdempotent

Returns the French authority a raffle is filed with for a postcode (the town hall of the commune, or the Préfecture de police for Paris): name, public address, e-mail, phone, website, online form, and the public directory source with the date it was read. When a postcode covers several communes, the commune name selects one.

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": {
      "postcode": "<postcode>"
    },
    "name": "find_authority"
  }
}

Input Schema

NameRequiredDescriptionDefault
communeNoCommune name, when the postcode covers several.
languageNoLanguage of the notice.
postcodeYesFrench postcode of the head office, five digits.

Output Schema

NameRequiredDescriptionDefault
kindYes
nameYes
emailYes
phoneYes
noticeYes
sourceYes
addressYes
websiteYes
form_urlYes

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 cover readOnly, idempotent, non-destructive and closed-world, so the bar is lower. The description still adds real context beyond them: it discloses that results come from a public directory with a read date, which tells the agent the data may be stale and has traceable provenance. It does not cover miss behaviour for unknown postcodes, which is the remaining gap.

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?

Two sentences, front-loaded with the core purpose and followed by the disambiguation rule. The enumerated return fields (name, address, e-mail, phone, website, form, source) are somewhat long given an output schema exists, but they communicate the record's shape efficiently without filler.

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 three-parameter read-only lookup with an output schema and full annotations, the description covers purpose, disambiguation, data provenance and returned fields. The only substantive omission is failure behaviour for an unmatched postcode or an ambiguous postcode with no commune supplied.

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%, so all three parameters including the language enum are already documented in the schema. The description only adds meaning for one of them — 'When a postcode covers several communes, the commune name selects one' — which usefully explains the disambiguation rule but leaves language unexplained beyond the schema.

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?

The description opens with a specific verb and resource: 'Returns the French authority a raffle is filed with for a postcode', and immediately narrows the scope (town hall of the commune, or Préfecture de police for Paris). An agent can tell this is a lookup of the filing authority, not a campaign-management operation like the sibling tools.

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 by the framing 'a raffle is filed with' — the agent must infer this is for determining where to file a declaration. No explicit when-to-use, when-not-to-use, or alternative is named, and no prerequisites are stated. The final clause about disambiguating by commune is parameter guidance rather than tool-selection guidance.

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