FFBB MCP Server

Overview Schema Source Related Servers Discussions Admin

Bilan détaillé de saison

ffbb_bilan_saison

Read-onlyIdempotent

Get a detailed season record for a specific basketball team, aggregating all phases and pools. See standings, games played, wins, losses, draws, points scored, conceded, and total balance.

Instructions

Bilan détaillé de la saison pour une équipe précise (toutes phases).

Cet outil est optimisé pour les questions du type "Quel est le bilan de la saison des U11M1 ?".

Il agrège toutes les phases (toutes poules) de la saison FFBB pour l'équipe identifiée par (organisme_id/club_name, categorie, numero_equipe).

Pour chaque phase, il retourne :

competition
poule_id
position
match_joues, gagnes, perdus, nuls
paniers_marques, paniers_encaissés, difference

Et fournit également un champ bilan_total qui cumule toutes les phases.

Input Schema

TableJSON Schema

Name	Required	Description
`poule_id`	No	ID FFBB de la poule pour désambiguïser.
`categorie`	No	Catégorie + genre + numéro d'équipe facultatif (ex: 'U11M', 'U11M1', 'U13F2', 'SeniorM'). Cette valeur sert à filtrer les engagements et les poules.
`club_name`	No	Nom du club (ex: 'Stade Clermontois', 'ASVEL').
`season_id`	No	ID de la saison FFBB (optionnel).
`organisme_id`	No	ID FFBB du club (alternative plus rapide à club_name).
`engagement_id`	No	ID FFBB de l'engagement (prioritaire pour désambiguïser).
`force_refresh`	No	Si True, contourne le cache pour récupérer des données fraîches.
`numero_equipe`	No	Numéro d'équipe (1, 2, ...) pour identifier l'équipe précise dans la catégorie (défaut: 1).
`competition_id`	No	ID FFBB de la compétition pour désambiguïser.
`competition_type`	No	Type de compétition ('PLAT', 'COUPE', etc.) pour désambiguïser.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv1.13.0Sep 15, 2026

changedInput schema / anyOf

Previous value: -[
-  {
-    "required": [
-      "club_name"
-    ]
-  },
-  {
-    "required": [
-      "organisme_id"
-    ]
-  }
-]New value: +[
+  {
+    "required": [
+      "organisme_id"
+    ]
+  },
+  {
+    "required": [
+      "club_name"
+    ]
+  },
+  {
+    "required": [
+      "engagement_id"
+    ]
+  },
+  {
+    "required": [
+      "poule_id"
+    ]
+  },
+  {
+    "required": [
+      "competition_id"
+    ]
+  }
+]

addedInput schema / properties / competition_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "ID FFBB de la compétition pour désambiguïser.",
+  "title": "Competition Id"
+}

addedInput schema / properties / competition_type

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Type de compétition ('PLAT', 'COUPE', etc.) pour désambiguïser.",
+  "title": "Competition Type"
+}

addedInput schema / properties / engagement_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "ID FFBB de l'engagement (prioritaire pour désambiguïser).",
+  "title": "Engagement Id"
+}

changedInput schema / properties / numero_equipe / default
```
Previous value: -1New value: +null
```

addedInput schema / properties / poule_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "ID FFBB de la poule pour désambiguïser.",
+  "title": "Poule Id"
+}

addedInput schema / properties / season_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "ID de la saison FFBB (optionnel).",
+  "title": "Season Id"
+}

Changed2 schema fields changedv1.9.0Sep 5, 2026

addedInput schema / anyOf

Added value: +[
+  {
+    "required": [
+      "club_name"
+    ]
+  },
+  {
+    "required": [
+      "organisme_id"
+    ]
+  }
+]

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": true,
-  "title": "ffbb_bilan_saisonDictOutput",
-  "type": "object"
-}New value: +null

Changed13 schema fields changedv1.8.0Aug 29, 2026

addedInput schema / properties / categorie / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / categorie / default
```
Added value: +null
```

changedInput schema / properties / categorie / description

Previous value: -"Catégorie + genre (ex: 'U11M', 'U13F', 'SeniorM'). Cette valeur sert à filtrer les engagements et les poules."New value: +"Catégorie + genre + numéro d'équipe facultatif (ex: 'U11M', 'U11M1', 'U13F2', 'SeniorM'). Cette valeur sert à filtrer les engagements et les poules."

removedInput schema / properties / categorie / type
```
Removed value: -"string"
```

addedInput schema / properties / club_name

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Nom du club (ex: 'Stade Clermontois', 'ASVEL').",
+  "title": "Club Name"
+}

addedInput schema / properties / numero_equipe / anyOf

Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / numero_equipe / default
```
Added value: +1
```

changedInput schema / properties / numero_equipe / description

Previous value: -"Numéro d'équipe (1, 2, ...) pour identifier l'équipe précise dans la catégorie."New value: +"Numéro d'équipe (1, 2, ...) pour identifier l'équipe précise dans la catégorie (défaut: 1)."

removedInput schema / properties / numero_equipe / type
```
Removed value: -"integer"
```

changedInput schema / properties / organisme_id / anyOf

Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "string"
-  }
-]New value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / organisme_id / default
```
Added value: +null
```

changedInput schema / properties / organisme_id / description

Previous value: -"ID FFBB du club (organisme) concerné."New value: +"ID FFBB du club (alternative plus rapide à club_name)."

removedInput schema / required

Removed value: -[
-  "organisme_id",
-  "categorie",
-  "numero_equipe"
-]

Addedv1.3.2May 23, 2026
Removedv1.3.1May 21, 2026
Addedv1.2.0May 1, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, and non-destructive behavior. The description adds useful behavioral context: it aggregates all phases, returns per-phase statistics, and provides a cumulative bilan_total. No contradiction with annotations.

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?

The description is front-loaded with the purpose, followed by a concise bullet list of return fields. There is slight repetition of 'toutes phases', but the overall structure is clear and economical.

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?

Despite having 10 parameters and no output schema, the description covers the tool's use case, identification logic, aggregation behavior, and return fields. Optional disambiguation parameters are left to the schema, which is reasonable given the 100% schema coverage.

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 the schema already documents the parameters. The description usefully groups the team identification parameters (organisme_id/club_name, categorie, numero_equipe), but it does not add much per-parameter meaning beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the resource and action: a detailed season record for a specific team, covering all phases. It also gives an example question and lists the returned fields. It does not explicitly name a sibling alternative, so it stops short of full differentiation.

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

Usage Guidelines4/5

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

The description explicitly frames the tool as optimized for questions like 'Quel est le bilan de la saison des U11M1 ?', giving an agent a clear trigger for when to use it. It does not state when not to use it or mention alternatives such as ffbb_bilan.

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

Deploy Server

Bilan détaillé de saison

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools