Skip to main content
Glama
nickdesi

FFBB MCP Server

by nickdesi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Recherche dans les règlements sportifs FFBB

ffbb_search_regulations
Read-onlyIdempotent

Look up FFBB, regional, and departmental regulations by keywords to identify relevant articles on qualifications, promotions, youth brackets, technical rules, and forfeits when the article number is unknown.

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

TableJSON 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
Behavior5/5

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

Annotations already convey read-only, idemponent, non-destructive traits, but the description adds extra behavioral details not in annotations: deterministic search, SWR cache, sorted by relevance, and a precise return dict shape. This materially helps the agent predict side effects and output structure.

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?

Every sentence pulls weight: scope, examples of relevant topics, return format, side-effect disclosure, explicit routing to siblings, and parameter-narrowing advice. It is front-loaded with the core purpose, and no filler appears.

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?

Given seven parameters, no required args, no output schema, and many siblings, this description is remarkably complete. It tells what the tool returns, sorts by relevance, is read-only and idemponent, and exactly which sibling should be used in adjacent cases. Nothing critical is missing for correct selection and invocation.

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%, so the baseline is 3 and the schema fully explains each parameter. The description contributes only a heuristic tip to narrow with level/organizer/category/limit and a few query examples, but no additional semantic information beyond the schema descriptions. This meets the baseline without exceeding it.

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?

A clear, specific verb and resource: full-text search in official FFBB regulations, and scope is narrowed to federal/regional/departmental. The description names the most relevant siblings to avoid confusion and defines what the tool is not for (retrieving an article, listing docs, explaining tiebreaks), so an agent can tell it apart without opening schemas.

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?

It explicitly states when to use this tool (when the article number is unknown and searching by keywords) and when not to use it, naming ffbb_get_regulation_article, ffbb_list_regulations, and ffbb_explain_tiebreak_rules as alternatives. It even advises narrowing with level, organizer, category, and limit, leaving little 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