Skip to main content
Glama
nickdesi

FFBB MCP Server

by nickdesi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Dernier résultat d'équipe

ffbb_last_result
Read-onlyIdempotent

Retrieve the final score and outcome of a single team's most recently played game. Specify club, category, competition, or FFBB IDs to get the result.

Instructions

Dernier résultat d'une équipe précise.

SINGULIER UNIQUEMENT: retourne le dernier match joué d'une seule équipe. 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
NameRequiredDescriptionDefault
poule_idNoID FFBB de la poule pour désambiguïser.
categorieNoCatégorie de l'équipe précise (ex: 'U11M1', 'U11M', 'SEM1', 'NM3').
club_nameNoNom du club (ex: 'Stade Clermontois')
season_idNoID de la saison FFBB (optionnel).
organisme_idNoIdentifiant FFBB du club (organisme_id, ex: '9326' ou 'ARA0063058').
engagement_idNoID FFBB de l'engagement (prioritaire pour désambiguïser).
force_refreshNoSi True, force un rafraichissement des donnees de poule
numero_equipeNoNuméro d'équipe dans la catégorie. Résoudre avec ffbb_resolve_team si ambigu.
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. Changed15 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 / 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"
-]
  2. 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_last_resultDictOutput",
-  "type": "object"
-}New value: +null
  3. Changed2 schema fields changedv1.5.1
    • 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')"
  4. Addedv1.3.2
  5. Removedv1.3.1
  6. Addedv1.2.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior. The description adds useful behavioral nuance beyond annotations: the tool only handles one team at a time and may need an exact resolved `numero_equipe` for ambiguous categories. No contradiction with the readOnlyHint.

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 short and front-loaded, with the core singular-only behavior stated first and the resolver recommendation as a targeted extra. The first two sentences are slightly redundant, but the whole thing remains 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?

Together with the rich schema and annotations, the description is sufficiently complete: it specifies the return scope, emphasizes singularity, and gives a concrete disambiguation workflow. There is no output schema, so a note on the exact result fields would be an enhancement, but it is not a blocker.

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?

Schema description coverage is 100% and every parameter already has a meaningful description, including the resolver note on `numero_equipe`. The tool description adds no new per-parameter meaning, so the baseline score of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the operation: 'retourne le dernier match joué d'une seule équipe' (returns the last played match of a single team), with a specific resource and scope. It emphasizes singular-only behavior, which distinguishes it from any batch or team-wide tools, though it does not explicitly name sibling alternatives.

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?

It gives a direct LLM recommendation: if the category is imprecise or lacks a number, call `ffbb_resolve_team` first to obtain the real `numero_equipe`. It also makes the singular-only constraint explicit. It does not mention exclusions or compare against sibling tools such as `ffbb_next_match`, but the context is clear enough.

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