FFBB MCP Server

by nickdesi

Overview Schema Source Related Servers Discussions Admin

Python

Remote

Bilan détaillé de saison

ffbb_bilan_saison

Read-onlyIdempotent

Bilan multi-phases approfondi d'une équipe sur la saison (phases 1/2, coupes, play-offs).

Instructions

Bilan multi-phases approfondi d'une équipe sur la saison (phases 1/2, coupes, play-offs).

Agrège le parcours successif avec cumul saisonnier. Pour une synthèse rapide, préférer `ffbb_team_summary`.

Input 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

Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds the aggregation behaviour ('parcours successif avec cumul saisonnier'), which is real context, but says nothing about cost, latency, caching behaviour (despite a `force_refresh` param), or result shape.

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?

Three short lines: scope first, behaviour second, alternative routing last. No filler, and the most decision-relevant information is front-loaded.

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

Completeness3/5

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

With 10 parameters, an anyOf-required identity resolution scheme and no output schema, the description leaves the agent to infer how to pick among the five identity inputs and what the report actually returns beyond 'multi-phases'. The routing hint helps, but for this complexity the description is thin.

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 every parameter is documented in the schema (including the identity-resolution alternatives and `force_refresh`). The description adds no parameter-level guidance, so the baseline 3 applies.

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 names a specific operation (a detailed multi-phase season report for a team) and scopes the content to phases 1/2, cups and play-offs. It also explicitly distinguishes itself from `ffbb_team_summary`, so an agent can tell the two apart without opening either schema.

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?

It gives an explicit routing rule: for a quick synthesis, prefer `ffbb_team_summary`, which implies this tool is for the deep, multi-phase analysis. No exclusion or prerequisite is stated for this tool itself, so it falls short of a full when/when-not pair.

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

Bilan détaillé de saison

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools