Skip to main content
Glama
nickdesi

FFBB MCP Server

by nickdesi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Liste des saisons FFBB

ffbb_saisons
Read-onlyIdempotent

Get the full list of FFBB seasons with IDs, labels, start/end dates, and active flags. Use these season IDs to filter data in other FFBB tools like bilan, club, or team summary.

Instructions

Liste des saisons FFBB (référentiel temporel).

Retourne la liste complète des saisons FFBB sous forme list[dict] triée chronologiquement, chaque entrée contenant id (et alias season_id), libelle (et alias label), debut, fin, enCours (booléen, calculé via debut <= today <= fin), code, actif et within_date_range (booléen). Lecture seule, idempotent, sans effet de bord ni écriture. Cache SWR avec TTL long (≈24h) ; force_refresh=True contourne le cache pour données fraîches et active_only=True filtre côté serveur pour ne garder que la saison active.

Utilise cet outil pour récupérer les id / season_id de saison disponibles avant d'appeler ffbb_bilan, ffbb_club ou ffbb_team_summary avec un filtre de saison. Ne pas utiliser pour obtenir un classement, un calendrier ou un bilan — utilise ffbb_club(action="classement") ou ffbb_bilan à la place ; pour la version du serveur, utilise ffbb_version.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
active_onlyNoTrue = saison active uniquement.
force_refreshNoSi True, contourne le cache.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.13.0
    • addedInput schema / properties / force_refresh
      Added value: +{
+  "default": false,
+  "description": "Si True, contourne le cache.",
+  "title": "Force Refresh",
+  "type": "boolean"
+}
  2. Changed1 schema field changedv1.9.0
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "items": {
-        "additionalProperties": true,
-        "type": "object"
-      },
-      "title": "Result",
-      "type": "array"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "ffbb_get_saisonsOutput",
-  "type": "object"
-}New value: +null
  3. Addedv1.3.2
  4. Removedv1.3.1
  5. Addedv1.2.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations, the description transparently discloses cache behavior with SWR and a ~24h TTL, explains that force_refresh bypasses the cache, and describes computed fields like enCours and within_date_range. It also confirms the read-only, idempotent, side-effect-free nature, which is consistent with the annotations. No 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.

Conciseness5/5

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

The description is dense but efficient, front-loading the core purpose and return shape before moving to behavior, parameters, and usage routing. Every section earns its place, and the explicit usage/alternative guidance avoids the need for further inference.

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?

With no output schema, the description compensates by fully specifying the return type and the fields inside each dict, including aliases and computed booleans. It also covers cache behavior, parameter effects, and routing to sibling tools, making the tool complete for an agent to invoke correctly without additional lookups.

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?

The schema already covers both parameters with 100% description coverage, so the baseline is 3, but the tool description adds meaning beyond the schema by explaining that force_refresh provides fresh data and that active_only filters server-side. This gives the agent a clearer sense of the practical effect of each parameter, though the schema already provides the basic semantic.

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 clearly states the tool returns the complete list of FFBB seasons as a chronologically sorted list[dict], with a detailed field breakdown. It also distinguishes itself from sibling tools by explicitly saying it is not for rankings, calendars, or bilan, and names the alternatives. This makes the tool's purpose unmistakable.

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 guidance: retrieve season ids before calling ffbb_bilan, ffbb_club, or ffbb_team_summary with a season filter. It also provides when-not-to-use guidance and names the correct alternatives for rankings, bilan, and server version, so an agent can route correctly.

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