Skip to main content
Glama
nickdesi

FFBB MCP Server

by nickdesi

Outils agrégés club

ffbb_club
Read-onlyIdempotent

Retrieve a French basketball club's schedule, teams, and standings from FFBB. Use 'calendrier' for all past and future matches, 'equipes' for team lists, or 'classement' for rankings. Filters available by category or team number.

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)`.

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 a effectuer pour le club.
club_nameNoNom du club (recommande, ex: 'Stade Clermontois'). Si absent, `organisme_id` doit etre fourni.
organisme_idNoIdentifiant FFBB du club. Si absent, `club_name` est utilise pour effectuer une recherche.
filtreNoFiltre facultatif de categorie/genre (ex: 'U11', 'U11M', 'U11F'). Utilise pour restreindre les equipes et poules.
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.
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=true and idempotentHint=true. Description adds context on reliability, calendar limitations of ffbb_get, and cache bypass via force_refresh, which is valuable beyond annotations.

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?

Four concise sentences, front-loaded with purpose, then usage guidance and warning. Every sentence earns its place; no redundancy.

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 8 parameters, 100% coverage, annotations, and an output schema, the description ties together use cases, sibling tools, and warnings, making it fully adequate for an aggregated tool.

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% (baseline 3). Description adds extra context on action='calendrier' being most reliable and force_refresh for cache, thus adding value beyond 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 clearly states the tool aggregates club tools (calendar, teams, standings) and specifies the resource (club). It distinguishes from siblings by explicitly recommending alternatives for specific team scores/matches.

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?

Provides explicit when-to-use (plural requests, full calendar without limitations) and when-not-to-use (specific score/next match) with named alternatives (ffbb_last_result, ffbb_next_match).

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