FFBB MCP Server

by nickdesi

Overview Schema Source Related Servers Discussions Admin

Python

Remote

Résolution d'équipe

ffbb_resolve_team

Read-onlyIdempotent

Identifie une equipe unique (Pivot central).

Instructions

Identifie une equipe unique (Pivot central).

DOIT etre utilise avant `ffbb_next_match` ou `ffbb_last_result` si l'agent
ne connait pas le numero d'equipe exact ou si la categorie est ambiguë (ex: 'U11M').
Pour une équipe senior au niveau national ou régional, la catégorie FFBB interne est souvent `SEM1` ou `SEF1` ;
le serveur résout désormais `NM3`, `NM2`, `NF1`, `PNM`, `R2`, etc. vers la bonne équipe et sa poule.

Politique : si une catégorie sans numéro (ex: 'U18M') correspond à plusieurs équipes (ex: U18M1, U18M2),
retourne 'ambiguous' (confiance 0.5) sans trancher arbitrairement.
Pour des suggestions heuristiques ordonnées (U18M1 à 0.85), utiliser `ffbb_find_team_candidates`.

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 (ex: 'U11M1', 'U13F2', 'SEM1') ou division (ex: 'NM3', 'R2', 'PNM'). Si le numéro manque, cet outil retourne la bonne équipe ou des candidats.
`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, force le rafraîchissement des données.
`numero_equipe`	No	Numéro d'équipe facultatif (ex: 1, 2).
`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"
+}

addedInput schema / properties / force_refresh

Added value: +{
+  "default": false,
+  "description": "Si True, force le rafraîchissement des données.",
+  "title": "Force Refresh",
+  "type": "boolean"
+}

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"
+}

Changed1 schema field changedv1.10.0Sep 6, 2026

changedInput schema / properties / categorie / description

Previous value: -"Catégorie + genre + numéro d'équipe (ex: 'U11M1', 'U13F2', 'U15M'). Si le numéro manque, cet outil retourne la bonne équipe ou des candidats."New value: +"Catégorie + genre + numéro d'équipe (ex: 'U11M1', 'U13F2', 'SEM1') ou division (ex: 'NM3', 'R2', 'PNM'). Si le numéro manque, cet outil retourne la bonne équipe ou des candidats."

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_resolve_teamDictOutput",
-  "type": "object"
-}New value: +null

Changed1 schema field changedv1.8.0Aug 29, 2026

addedInput schema / properties / numero_equipe

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Numéro d'équipe facultatif (ex: 1, 2).",
+  "title": "Numero Equipe"
+}

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

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), so the bar is lower, yet the description still adds real behavior: on an ambiguous category it returns 'ambiguous' with confidence 0.5 rather than guessing, and it documents which external division codes (NM3, NM2, NF1, PNM, R2) the server now resolves. It does not describe caching/force_refresh effects, so it stops short of a 5.

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?

Purpose and the pre-requisite order are front-loaded, and the ambiguity policy is stated crisply. The 'le serveur résout désormais ...' sentence reads like a changelog note and could be trimmed without losing instruction value.

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?

For a 10-parameter resolver with no output schema and no required fields, the description covers the essential contract: it says a single team is returned, that disambiguation inputs exist, and what happens on ambiguity. It stops short of describing the full return shape (fields for success, team id, candidate lists), which the absent output schema would otherwise have carried.

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 schema already documents category formats, IDs and disambiguation roles; the baseline is 3. The description's category example ('SEM1'/'SEF1', division codes) largely restates the schema field description, adding only marginal meaning beyond 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?

The description opens with a specific verb+resource ('Identifie une equipe unique') and frames the tool as the central pivot of team resolution. It explicitly distinguishes itself from siblings ffbb_next_match, ffbb_last_result and ffbb_find_team_candidates, so an agent can pick it without opening any schema.

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 states the trigger condition precisely: use before ffbb_next_match/ffbb_last_result when the exact team number is unknown or the category is ambiguous (e.g. 'U11M'). It also routes to the correct alternative for a different need ('Pour des suggestions heuristiques ordonnées ... utiliser ffbb_find_team_candidates'), covering both when-to-use and when-to-use-something-else.

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

Résolution d'équipe

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools