Skip to main content
Glama
nickdesi

FFBB MCP Server

by nickdesi

Outils agrégés club

ffbb_club
Read-onlyIdempotent

Retrieve club schedules, standings, and team lists. Use calendar action to get all past and future matches for a team or category.

Instructions

Outils agreges autour d'un club (calendrier, equipes, classement).

✅ Outil de référence pour toute demande au pluriel : "matchs restants", "derniers matchs à jouer", "prochaines journées", "calendrier de fin de saison".

action="calendrier" est l'outil le plus fiable pour obtenir TOUTES les rencontres passées et futures d'une équipe/catégorie, sans les limitations de ffbb_get(poule).

🎯 Pour isoler les confrontations directes entre deux équipes : Utilise le paramètre adversaire avec action="calendrier". Exemple : confrontations Royat vs Pont-du-Château en phase 3 → ffbb_club(action="calendrier", club_name="Pont du Chateau", filtre="U11M", adversaire="Royat Orcines", numero_equipe=1)

Avertissement: ne pas utiliser pour obtenir un score ou un prochain match d'une equipe specifique. Utiliser ffbb_last_result et ffbb_next_match a la place.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction club. Utiliser 'calendrier' pour les demandes au pluriel (matchs restants, calendrier, prochaines journées).
club_nameNoNom du club (recommande, ex: 'Stade Clermontois'). Si absent, `organisme_id` doit etre fourni.
organisme_idNoIdentifiant FFBB du club (ex: 1234 ou 'ARA0063058'). Si absent, `club_name` est utilise pour effectuer une recherche.
filtreNoFiltre facultatif de categorie/genre (ex: 'U11', 'U11M', 'U11F'). Pour une équipe précise, compléter avec numero_equipe.
adversaireNoNom de l'équipe adversaire pour filtrer uniquement les confrontations directes (ex: 'Royat Orcines', 'Stade Clermontois'). Utilisé avec action='calendrier'. Insensible à la casse et aux accents.
poule_idNoIdentifiant de la poule (obligatoire pour action='classement' si aucun filtre ne permet de determiner la poule).
numero_equipeNoNuméro d'équipe facultatif (ex: 1, 2, 3). Utilisé avec action='calendrier' pour ne récupérer que les matchs de cette équipe précise.
phaseNoNom ou numéro de la phase (ex: 'Phase 3', '2'). Utilisé avec action='classement' pour auto-résoudre la poule.
date_debutNoDate de début de filtrage au format YYYY-MM-DD (ex: '2026-05-01').
date_finNoDate de fin de filtrage au format YYYY-MM-DD (ex: '2026-05-31').
limitNoNombre maximum de matchs de calendrier à retourner (pagination/limite).
force_refreshNoSi True, contourne le cache pour les donnees de calendrier ou de classement (utile les jours de match).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds behavioral context: it states the tool is the most reliable for obtaining all matches, mentions cache behavior with force_refresh, and notes limitations of alternative tools (ffbb_get). No contradictions.

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?

The description is concise and well-structured with emojis and sections, front-loading the purpose and quickly conveying key guidance. Every sentence adds value, and there is no wasted text.

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 the tool's complexity (12 parameters, 3 actions, external output schema), the description is remarkably complete. It covers usage scenarios, parameter combinations, caching behavior, and differentiation from siblings. The presence of an output schema ensures return values are documented elsewhere.

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%, so baseline is 3. The description enriches parameters by promoting action='calendrier' as most reliable, explaining adversaire usage with a concrete example, and giving usage hints for filtre, numero_equipe, phase. This goes beyond the schema descriptions.

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 clearly states the tool provides aggregated club tools (calendar, teams, standings) and gives concrete examples of use cases like 'matchs restants' and 'prochaines journées'. It explicitly differentiates from sibling tools like ffbb_last_result and ffbb_next_match.

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?

The description provides explicit when-to-use and when-not-to-use guidance, including warnings to avoid using for single team scores or next match, directing to specific siblings. It explains the recommended action='calendrier' and how to filter with adversaire parameter, with an example.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nickdesi/FFBB-MCP-Server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server