Skip to main content
Glama
nickdesi

FFBB MCP Server

by nickdesi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Résumé complet d'équipe

ffbb_team_summary
Read-onlyIdempotent

Retrieve a full team summary - record, standings, last and next match - in one call. Resolves league codes (NM3, PNM) to the correct team and suggests candidates when ambiguous.

Instructions

Résumé complet d'équipe : bilan, classement, dernier et prochain match en un seul appel.

Résout NM3, PNM, NF1, etc. vers la bonne équipe. En cas d'ambiguïté, suggère les candidats.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
poule_idNoID FFBB de la poule pour désambiguïser.
categorieNoCatégorie/division + genre + numéro d'équipe (ex: 'U11M1', 'U13F2', 'SEM1', 'NM3', 'PNM').
club_nameNoNom du club (ex: 'Stade Clermontois', 'ASVEL').
season_idNoID de la saison FFBB (optionnel).
organisme_idNoID FFBB du club (alternative plus rapide à club_name).
engagement_idNoID FFBB de l'engagement (prioritaire pour désambiguïser).
force_refreshNoSi True, force un rafraichissement des donnees
numero_equipeNoNuméro d'équipe dans la catégorie (ex: 1, 2).
competition_idNoID FFBB de la compétition pour désambiguïser.
competition_typeNoType de compétition ('PLAT', 'COUPE', etc.) pour désambiguïser.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv1.13.0
    • 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"
+}
  2. Changed1 schema field changedv1.10.0
    • 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')."
  3. Changed2 schema fields changedv1.9.0
    • 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
  4. Changed2 schema fields changedv1.8.0
    • 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"
+}
  5. Addedv1.3.2
  6. Removedv1.3.1
  7. Addedv1.2.0

TDQS

A4.2/5.0
Behavior4/5

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

Read-only, open-world, and idempotent safety are already covered by annotations, so the description only needs to add behavior beyond that. It adds the resolution behavior for abbreviations like NM3/PNM/NF1 and the fallback of suggesting candidates on ambiguity. This is useful operational context not present in the schema.

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 description is compact and front-loaded: the first sentence states the primary result, and the second adds the important resolution/ambiguity behavior. Every sentence earns its place without repeating schema or annotation details.

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?

With 10 parameters and no output schema, the description covers the main gaps by enumerating the returned sections and explaining disambiguation and ambiguity handling. The anyOf parameter grouping is left to the schema, which is acceptable because the schema already describes it fully.

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?

The input schema has 100% property description coverage, so the baseline is 3. The description hints that category codes like NM3/PNM are resolveable, but most parameter meaning is already provided by the schema. No significant parameter-semantics value is added beyond that baseline.

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 that the tool returns a full team bundle (bilan, classement, dernier et prochain match) in a single call, which identifies a specific combined resource. The one-call phrasing differentiates it from sibling tools that cover only one component. The resolution of division codes (NM3, PNM, NF1) further clarifies its role.

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 description makes clear that the tool is for obtaining a complete team summary in one call rather than assembling it from separate sibling calls. It does not explicitly name alternative tools or state when not to use it, but the context is strong enough to guide selection.

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

Deploy Server

Other Tools