Skip to main content
Glama
Sign In
FFBB MCP Server

FFBB MCP Server

by nickdesi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Dernier résultat d'équipe

ffbb_last_result
Read-onlyIdempotent

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

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

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 declare readOnly, idempotent, non-destructive, openWorld. The description adds a genuine behavioral constraint beyond them: it returns a single team's last match only (singular scope), which shapes how the agent must call it. It omits return format/pagination, but the safety profile is already covered.

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?

Purpose is front-loaded, followed by the singular scope constraint and then the resolution recommendation in three short sentences. There is mild redundancy between 'dernier résultat d'une équipe précise' and 'le dernier match joué d'une seule équipe', but nothing wasteful.

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 read-only, idempotent tool with full schema coverage and no output schema, the definition covers purpose, scope and the disambiguation workflow adequately. It stops short of describing what the result payload contains, which is the only real gap given the absence of an output schema.

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%, so the schema already documents all 10 parameters, including the numero_equipe resolution hint. The description repeats the resolve_team cross-reference but adds no syntax or format detail beyond what the schema provides, so it sits at the baseline.

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 states a specific verb and resource ('retourne le dernier match joué') and reinforces scope with 'SINGULIER UNIQUEMENT'. It implies a plural/batch counterpart but never names the sibling (e.g. next_match or team_summary) that an agent should compare against.

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 an explicit workflow condition: when the categorie is imprecise or numeric, call ffbb_resolve_team first to obtain the real numero_equipe. That names an alternative and the condition selecting it, though it does not contrast this tool against ffbb_next_match or ffbb_match_lookup.

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