Skip to main content
Glama
Sign In
FFBB MCP Server

FFBB MCP Server

by nickdesi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Recherche dans les règlements sportifs FFBB

ffbb_search_regulations
Read-onlyIdempotent

Recherche plein texte déterministe dans les règlements officiels FFBB, régionaux et départementaux.

Instructions

Recherche plein texte déterministe dans les règlements officiels FFBB, régionaux et départementaux.

Permet de retrouver les articles pertinents sur les qualifications, montées/descentes,
brassages jeunes, règles techniques (durée, ballons, zone), forfaits et brûlage.
Retourne `dict` avec `results[]` (`id`, `document_id`, `article_number`, `article_title`, `relevance_score`, `content`, `topics[]`, `source_url`)
triés par pertinence ; lecture seule, idempotent, cache SWR.

Utilise cet outil quand tu ne connais pas le numéro d'article et que tu cherches par
mots-clés. Ne pas utiliser pour récupérer un article précis — utilise
`ffbb_get_regulation_article` à la place ; pour lister les documents — utilise
`ffbb_list_regulations` ; pour expliquer un départage — utilise
`ffbb_explain_tiebreak_rules` au lieu de chercher le texte. Affûte avec `level`,
`organizer`, `category` et `limit` pour réduire le bruit.

Input Schema

NameRequiredDescriptionDefault
levelNoNiveau de compétition ciblé : 'federal' (FFBB national / RSG / Élite), 'regional' (Ligues, ex: AURA), 'departmental' (Comités, ex: Comité 63)
limitNoNombre maximal d'extraits d'articles à retourner (défaut 5, max 10)
queryNoTerme ou question de recherche dans les règlements (ex: 'brûlage équipe réserve', 'défense de zone U13', 'brassages départementaux', 'barrages accession')
topicNoMots-clés thématiques (ex: 'departages', 'brulage', 'forfaits', 'poule_haute')
seasonNoSaison sportive ciblée (par défaut '2026-2027')2026-2027
categoryNoCatégorie d'âge ou division (ex: 'U13', 'U15', 'U18', 'seniors', 'elite')
organizerNoNom ou sigle de l'organisateur (ex: 'FFBB', 'Ligue AURA', 'Comité 63')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.13.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint, so the description's restatement of 'lecture seule, idempotent' earns no credit. It does add genuinely new behavior: deterministic search semantics, an SWR cache, and the full return shape (results[] sorted by relevance with id, document_id, article_number, relevance_score, content, topics, source_url). Minor deduction for the redundant safety restatement.

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?

Front-loaded with what the tool does, then return shape, then routing exclusions, then parameter tuning. Dense but every sentence carries a distinct payload; the result-field enumeration is justified since there is no output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description supplies the return structure itself; with 7 optional parameters, it supplies the tuning strategy. Combined with the explicit sibling routing, an agent has everything needed to call this correctly on the first try.

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 description coverage is 100%, so the baseline is 3 and the schema already carries syntax/defaults for all seven parameters. The description goes beyond it by telling the agent which parameters actually matter for noise reduction ('Affûte avec level, organizer, category et limit'), which is actionable guidance the schema does not provide.

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 ('Recherche plein texte déterministe dans les règlements officiels FFBB, régionaux et départementaux'), enumerates the subject matter covered (qualifications, montées/descentes, brassages, règles techniques, forfaits, brûlage), and is instantly distinguishable from the three named siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly states when to use it ('quand tu ne connais pas le numéro d'article et que tu cherches par mots-clés') and then names three alternatives with the condition that selects each: ffbb_get_regulation_article for a known article, ffbb_list_regulations for listing, ffbb_explain_tiebreak_rules for tiebreak explanations. Nothing is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools