Skip to main content
Glama
nickdesi

FFBB MCP Server

by nickdesi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Ressource FFBB par identifiant

ffbb_get
Read-onlyIdempotent

Fetch specific FFBB data (competitions, pools, clubs, matches, venues) using an exact ID and resource type.

Instructions

Recupere une ressource FFBB par identifiant.

  • type="competition" equivaut a get_competition. Si club est fourni, localise directement la poule du club au sein de la compétition.

  • type="poule" charge la poule (classements + rencontres).

  • type="organisme" charge les details d'un club.

  • type="engagement" charge les details d'un engagement d'équipe (club, poule, calendrier filtré).

  • type="rencontre" charge une rencontre précise.

  • type="salle" charge les details d'une salle et son adresse normalisée.

⚠️ Attention: type="poule" peut être tronqué si la poule est grande. Pour un calendrier exhaustif, préférez ffbb_club(action="calendrier").

Avertissement: ne pas utiliser pour obtenir un score ou un prochain match. Utiliser ffbb_last_result et ffbb_next_match a la place.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesIdentifiant FFBB exact (string opaque, ex: '200000003057825'). Ne pas passer un nom de club: utiliser d'abord ffbb_search pour résoudre l'id.
clubNoNom ou ID du club à localiser dans les poules (si type='competition'). Permet de trouver directement l'ID et le nom de poule d'un club dans une compétition multi-poules.
typeYesType de ressource a charger.
force_refreshNoSi True et type='poule', contourne le cache pour recuperer la poule en temps reel (scores live).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.16.4
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "competition",
-  "poule",
-  "organisme",
-  "rencontre",
-  "officiel",
-  "entraineur",
-  "salle"
-]New value: +[
+  "competition",
+  "poule",
+  "organisme",
+  "rencontre",
+  "officiel",
+  "entraineur",
+  "salle",
+  "engagement"
+]
  2. Changed3 schema fields changedv1.13.0
    • addedInput schema / properties / id / anyOf
      Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "string"
+  }
+]
    • changedInput schema / properties / id / description
      Previous value: -"Identifiant numérique FFBB exact. Ne pas passer un nom de club: utiliser d'abord ffbb_search pour résoudre l'id."New value: +"Identifiant FFBB exact (string opaque, ex: '200000003057825'). Ne pas passer un nom de club: utiliser d'abord ffbb_search pour résoudre l'id."
    • removedInput schema / properties / id / type
      Removed value: -"integer"
  3. Changed2 schema fields changedv1.10.0
    • addedInput schema / properties / club
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Nom ou ID du club à localiser dans les poules (si type='competition'). Permet de trouver directement l'ID et le nom de poule d'un club dans une compétition multi-poules.",
+  "title": "Club"
+}
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "competition",
-  "poule",
-  "organisme",
-  "rencontre",
-  "officiel",
-  "entraineur"
-]New value: +[
+  "competition",
+  "poule",
+  "organisme",
+  "rencontre",
+  "officiel",
+  "entraineur",
+  "salle"
+]
  4. Changed1 schema field changedv1.9.0
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "ffbb_getDictOutput",
-  "type": "object"
-}New value: +null
  5. Addedv1.3.2
  6. Removedv1.3.1
  7. Addedv1.2.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context: type='poule' can be truncated for large poules, force_refresh bypasses the cache for live scores, and the club parameter locates the club's poule within a competition. 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.

Conciseness4/5

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

The description is well-structured with a front-loaded summary, concise bullets, and short warning paragraphs. It is longer than minimal because there are eight resource types to cover, and most lines earn their place. A small redundancy exists between the 'Attention' and 'Avertissement' warnings, so it is not perfectly tight.

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 eight enum types, four parameters, and no output schema, the description covers most behavior: return content is described for competition, poule, organisme, engagement, rencontre, and salle, and important caveats such as truncation and cache bypass are included. However, the enum values 'officiel' and 'entraineur' are not explained, and no response shape is described.

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 operational meaning beyond the schema: id is an opaque FFBB identifier resolved via ffbb_search, club only applies to type='competition', and force_refresh is meaningful only for type='poule'. This extra context justifies a 4.

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 a specific verb and resource ('Récupère une ressource FFBB par identifiant') and immediately enumerates the supported resource types in bullet form. It also distinguishes itself from ffbb_last_result and ffbb_next_match, so an agent can tell it apart from siblings without opening the 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?

The description gives explicit routing guidance: type='competition' is equivalent to get_competition, exhaustive calendars should use ffbb_club(action='calendrier'), and score/next-match lookups should use ffbb_last_result and ffbb_next_match. It clearly states when to use this tool and when to use an alternative.

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