FFBB MCP Server

by nickdesi

Overview Schema Source Related Servers Discussions Admin

Python

Remote

Face-à-Face & Comparaison d'équipes (H2H)

ffbb_head_to_head

Read-onlyIdempotent

Compare two basketball teams' head-to-head history and current form to analyze their matchup.

Instructions

Compare deux équipes et analyse leurs confrontations directes (H2H) et dynamiques.

Input Schema

TableJSON Schema

Name	Required	Description
`club_a`	No	Nom du premier club (ex: 'Stade Clermontois').
`club_b`	No	Nom du second club / adversaire (ex: 'Vichy', 'Roanne').
`poule_id`	No	ID FFBB de la poule pour désambiguïser.
`categorie`	No	Catégorie d'équipe commune à comparer (ex: 'SEM1', 'U18M', 'Senior').
`club_name`	No	Alias pour club_a : nom du premier club (ex: 'Stade Clermontois').
`season_id`	No	ID de la saison FFBB (optionnel).
`adversaire`	No	Alias pour club_b : nom du second club / adversaire (ex: 'Vichy').
`organisme_id`	No	Alias pour organisme_id_a : ID FFBB du premier club.
`adversaire_id`	No	Alias pour organisme_id_b : ID FFBB du second club / adversaire.
`engagement_id`	No	ID FFBB de l'engagement partagé ou équipe A (alias pour engagement_id_a).
`force_refresh`	No	Si True, force le rafraîchissement des données
`competition_id`	No	ID FFBB de la compétition pour désambiguïser.
`organisme_id_a`	No	ID FFBB du premier club (ex: '9326').
`organisme_id_b`	No	ID FFBB du second club / adversaire.
`engagement_id_a`	No	ID FFBB de l'engagement équipe A (prioritaire).
`engagement_id_b`	No	ID FFBB de l'engagement équipe B (prioritaire).
`competition_type`	No	Type de compétition ('PLAT', 'COUPE', etc.) pour désambiguïser.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.14.5Sep 19, 2026

changedInput schema / anyOf

Previous value: -[
-  {
-    "required": [
-      "club_a"
-    ]
-  },
-  {
-    "required": [
-      "organisme_id_a"
-    ]
-  },
-  {
-    "required": [
-      "club_name"
-    ]
-  },
-  {
-    "required": [
-      "organisme_id"
-    ]
-  },
-  {
-    "required": [
-      "engagement_id_a"
-    ]
-  },
-  {
-    "required": [
-      "engagement_id"
-    ]
-  },
-  {
-    "required": [
-      "poule_id"
-    ]
-  }
-]New value: +[
+  {
+    "required": [
+      "club_a"
+    ]
+  },
+  {
+    "required": [
+      "organisme_id_a"
+    ]
+  },
+  {
+    "required": [
+      "club_name"
+    ]
+  },
+  {
+    "required": [
+      "organisme_id"
+    ]
+  },
+  {
+    "required": [
+      "engagement_id_a"
+    ]
+  },
+  {
+    "required": [
+      "engagement_id_b"
+    ]
+  },
+  {
+    "required": [
+      "engagement_id"
+    ]
+  },
+  {
+    "required": [
+      "poule_id"
+    ]
+  }
+]

Changed15 schema fields changedv1.13.0Sep 15, 2026

addedInput schema / anyOf

Added value: +[
+  {
+    "required": [
+      "club_a"
+    ]
+  },
+  {
+    "required": [
+      "organisme_id_a"
+    ]
+  },
+  {
+    "required": [
+      "club_name"
+    ]
+  },
+  {
+    "required": [
+      "organisme_id"
+    ]
+  },
+  {
+    "required": [
+      "engagement_id_a"
+    ]
+  },
+  {
+    "required": [
+      "engagement_id"
+    ]
+  },
+  {
+    "required": [
+      "poule_id"
+    ]
+  }
+]

addedInput schema / properties / adversaire

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Alias pour club_b : nom du second club / adversaire (ex: 'Vichy').",
+  "title": "Adversaire"
+}

addedInput schema / properties / adversaire_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Alias pour organisme_id_b : ID FFBB du second club / adversaire.",
+  "title": "Adversaire Id"
+}

changedInput schema / properties / club_b / description

Previous value: -"Nom du second club (ex: 'Vichy', 'Roanne')."New value: +"Nom du second club / adversaire (ex: 'Vichy', 'Roanne')."

addedInput schema / properties / club_name

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

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 partagé ou équipe A (alias pour engagement_id_a).",
+  "title": "Engagement Id"
+}

addedInput schema / properties / engagement_id_a

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

addedInput schema / properties / engagement_id_b

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

addedInput schema / properties / organisme_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Alias pour organisme_id_a : ID FFBB du premier club.",
+  "title": "Organisme Id"
+}

changedInput schema / properties / organisme_id_a / description

Previous value: -"ID FFBB du premier club (ex: 9326)."New value: +"ID FFBB du premier club (ex: '9326')."

changedInput schema / properties / organisme_id_b / description

Previous value: -"ID FFBB du second club."New value: +"ID FFBB du second club / adversaire."

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.9.0Sep 5, 2026

changedOutput schema / (root)

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

Addedv1.8.0Aug 29, 2026

TDQS

A3.7/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is well covered. The description adds no behavioral context such as data source, caching, or return semantics, but it does not contradict the annotations either.

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 a single front-loaded sentence with no filler. The word 'dynamiques' is slightly ambiguous and prevents a perfect score, but the structure is efficient.

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

Completeness2/5

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

This is a high-complexity tool with 17 parameters, multiple alias groups, no output schema, and no required fields. The description only states the purpose and leaves the agent to infer which parameter combination to supply and what the response will contain, so it is incomplete for correct invocation.

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?

All 17 parameters have schema descriptions, so the schema carries the semantic load and the baseline is 3. The description adds no guidance on alias groups or preferred identification methods (names vs IDs vs engagement IDs), which is a missed opportunity but not a deficiency given 100% schema coverage.

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 uses 'Compare' as a specific verb, identifies 'deux équipes' as the resource, and explicitly mentions H2H, which distinguishes this tool from the single-team sibling tools like ffbb_team_summary or ffbb_last_result. The word 'dynamiques' is slightly vague, but the core purpose is unmistakable.

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 imperative 'Compare deux équipes' and the mention of 'confrontations directes (H2H)' make the intended use case clear: any request for a two-team head-to-head comparison. It does not explicitly name alternatives or give when-not-to-use conditions, so it falls short of full routing guidance.

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

Deploy Server

Face-à-Face & Comparaison d'équipes (H2H)

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools