FFBB MCP Server

Overview Schema Source Related Servers Discussions Admin

Prochain match d'équipe

ffbb_next_match

Read-onlyIdempotent

Find the next upcoming match for a specific basketball team. Returns the single next game for a club and category to help plan upcoming fixtures.

Instructions

Prochain match à jouer pour une équipe précise.

⚠️ SINGULIER UNIQUEMENT. Si la demande est au pluriel ("matchs restants", "derniers matchs à jouer", "calendrier"), utiliser ffbb_club(action="calendrier") à la place.

⚠️ ATTENTION LLM : Cet outil retourne STRICTEMENT LE PROCHAIN MATCH UNIQUE. Ne l'utilise JAMAIS si l'utilisateur demande "les prochains matchs" au pluriel. Pour toute requête au pluriel, utilise OBLIGATOIREMENT ffbb_club(action="calendrier") et filtre les résultats toi-même.

Recommendation LLM : Si la categorie est imprécise ou sans numéro (ex: 'U11M'), appeler d'abord ffbb_resolve_team pour obtenir le numero_equipe reel.

Input Schema

TableJSON Schema

Name	Required	Description
`poule_id`	No	ID FFBB de la poule pour désambiguïser.
`categorie`	No	Catégorie de l'équipe précise (ex: 'U11M1', 'U11M', 'SEM1', 'NM3').
`club_name`	No	Nom du club (ex: 'Stade Clermontois')
`season_id`	No	ID de la saison FFBB (optionnel).
`organisme_id`	No	Identifiant FFBB du club (organisme_id, ex: '9326' ou 'ARA0063058').
`engagement_id`	No	ID FFBB de l'engagement (prioritaire pour désambiguïser).
`force_refresh`	No	Si True, force un rafraichissement des donnees de poule
`numero_equipe`	No	Numéro d'équipe dans la catégorie. Résoudre avec ffbb_resolve_team si ambigu.
`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.

Changed15 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 / 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 de l'équipe précise (ex: 'U11M1', 'U11M', 'U11F')"New value: +"Catégorie de l'équipe précise (ex: 'U11M1', 'U11M', 'SEM1', 'NM3')."

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

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 / numero_equipe / anyOf

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

changedInput schema / properties / numero_equipe / default
```
Previous value: -1New value: +null
```
removedInput schema / properties / numero_equipe / type
```
Removed value: -"integer"
```

changedInput schema / properties / organisme_id / description

Previous value: -"Identifiant FFBB du club (organisme_id, ex: 1234 ou 'ARA0063058')"New value: +"Identifiant FFBB du club (organisme_id, ex: '9326' ou 'ARA0063058')."

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

removedInput schema / required
```
Removed value: -[
-  "categorie"
-]
```

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

Changed2 schema fields changedv1.5.1Jun 9, 2026

changedInput schema / properties / organisme_id / anyOf

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

changedInput schema / properties / organisme_id / description

Previous value: -"Identifiant FFBB du club (organisme_id)"New value: +"Identifiant FFBB du club (organisme_id, ex: 1234 ou 'ARA0063058')"

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

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds useful behavioral context beyond annotations, notably that the tool returns STRICTLY ONE next match and should never be used for plural requests. No annotation contradiction exists.

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 core purpose and the critical singular-only constraint. The warnings about plural requests are somewhat repeated, but each repetition reinforces an important failure mode Lewis: 'ATTENTION LLM' is redundant with the earlier warning yet still earns its place due to the high cost of misuse.

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 tool with 10 parameters, an anyOf selection constraint, and no output schema, the description provides critical routing and parameter-resolution guidance. It does not fully explain how to choose among organisme_id, club_name, engagement_id, poule_id, and competition_id, but the schema descriptions largely cover those fields, and the description covers the main ambiguity traps.

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 description coverage is 100%, so the baseline is 3. The description adds extra semantic guidance by explaining that an imprecise category such as 'U11M' should first be resolved via ffbb_resolve_team to get the real numero_equipe, which clarifies how to use the categorie and numero_equipe parameters together.

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 states a specific verb plus resource: 'Prochain match à jouer pour une équipe précise.' This clearly distinguishes it from siblings like ffbb_last_result and ffbb_club(action="calendrier") by emphasizing the singular next match for one team.

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?

The description gives explicit when-to-use and when-not-to-use guidance: use it only for singular next-match requests, and use ffbb_club(action="calendrier") for plural requests. It also recommends ffbb_resolve_team when the category lacks a number, directly steering the agent to the correct alternative.

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

Deploy Server

Prochain match d'équipe

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools