FFBB MCP Server

Overview Schema Source Related Servers Discussions Admin

Résumé complet d'équipe

ffbb_team_summary

Read-onlyIdempotent

Retrieve a full team summary in a single call: overall record, current ranking, last match result, and upcoming fixture for any FFBB team.

Instructions

Résumé complet et agent-friendly pour une équipe.

Combine en UN seul appel :

bilan global (toutes phases)
phase courante et son classement
dernier match joué
prochain match à venir

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. Recommandé pour une vue rapide d'une équipe précise. Si la catégorie est ambiguë ou sans numéro d'équipe, l'outil tente une résolution via ffbb_resolve_team. Pour une liste de matchs restants, utiliser plutôt ffbb_club(action="calendrier").

Input Schema

TableJSON Schema

Name	Required	Description
`poule_id`	No	ID FFBB de la poule pour désambiguïser.
`categorie`	No	Catégorie/division + genre + numéro d'équipe (ex: 'U11M1', 'U13F2', 'SEM1', 'NM3', 'PNM').
`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 un rafraichissement des donnees
`numero_equipe`	No	Numéro d'équipe dans la catégorie (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.

Changed9 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 / 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"
```

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', 'Senior')."New value: +"Catégorie/division + genre + numéro d'équipe (ex: 'U11M1', 'U13F2', 'SEM1', 'NM3', 'PNM')."

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

Changed2 schema fields changedv1.8.0Aug 29, 2026

addedInput schema / properties / force_refresh

Added value: +{
+  "default": false,
+  "description": "Si True, force un rafraichissement des donnees",
+  "title": "Force Refresh",
+  "type": "boolean"
+}

addedInput schema / properties / numero_equipe

Added value: +{
+  "default": 1,
+  "description": "Numéro d'équipe dans la catégorie (ex: 1, 2).",
+  "title": "Numero Equipe",
+  "type": "integer"
+}

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

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds non-obvious behavioral context: it combines several data types into one call, resolves labels like NM3/PNM server-side, and falls back to ffbb_resolve_team on ambiguous categories. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The bulleted 'Combine en UN seul appel' block front-loads the core aggregation behavior, followed by a compact paragraph covering resolution rules and the sibling alternative. Every sentence earns its place without filler.

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

Completeness5/5

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

For a 10-parameter tool with anyOf-based identifiers and no output schema, the description covers what the summary contains, how identifiers are resolved, when to prefer this tool, and which sibling handles remaining-match lists. Parameter details are fully covered by the schema, so nothing essential is missing.

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 real parameter context by showing accepted category examples like SEM1, NM3, and PNM, and by clarifying how ambiguous or missing team numbers trigger resolution, which goes beyond the schema's generic category format.

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 'Résumé complet et agent-friendly pour une équipe' and then explicitly enumerates what the call aggregates: bilan global, phase courante/classement, dernier match, and prochain match. This is a specific verb-resource statement that clearly distinguishes it from narrower siblings like ffbb_bilan or ffbb_last_result.

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 'Recommandé pour une vue rapide d'une équipe précise', explains when category resolution applies via ffbb_resolve_team, and explicitly defers remaining-match lists to ffbb_club(action='calendrier'). This gives the agent both positive selection criteria and a clear exclusion.

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

Deploy Server

Résumé complet d'équipe

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools