Skip to main content
Glama
nickdesi

FFBB MCP Server

by nickdesi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Recherche et désambiguïsation d'équipes candidates

ffbb_find_team_candidates
Read-onlyIdempotent

Recherche et ordonne les équipes candidates d'un club/CTC pour désambiguïser avant tout calendrier/résultat.

Instructions

Recherche et ordonne les équipes candidates d'un club/CTC pour désambiguïser avant tout calendrier/résultat.

Évite la confusion entre équipe fanion sans numéro (ex: U13F en régional) et équipe réserve (ex: U13F2 en départemental).
Retourne la liste des candidats triés avec confiance, motif, détails de compétition et prochain match.

Politique : contrairement à `ffbb_resolve_team` (garde-fou strict), recommande l'équipe fanion (confiance 0.85) en l'absence de numéro.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sexeNoGenre de l'équipe ('M', 'F' ou 'MIXTE').
categorieNoCatégorie, étiquette ou division demandée (ex: 'U13F1', 'U13F', 'U15M', 'NM3', 'Senior'). L'outil extrait tranche d'âge, genre et numéro recherchés pour isoler les candidats.
club_nameNoNom du club ou de la CTC (ex: 'Cournon', 'Stade Clermontois'). Requis si organisme_id absent.
season_idNoID de la saison FFBB (optionnel).
organisme_idNoID FFBB du club (ex: '9289'). Requis si club_name absent.
force_refreshNoSi True, force le rafraîchissement des données.
numero_equipeNoNuméro d'équipe facultatif (ex: 1, 2).
include_next_matchNoSi True (défaut), récupère le prochain match programmé pour chaque candidat.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.15.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive). The description adds real behavior: it returns the sorted candidate list with confidence, motif, competition details, and next match, and discloses the tie-breaking policy (fanion recommended with confidence 0.85 absent a number). It stops short of any rate-limit or pagination note, but the disclosure is well beyond the 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?

Four sentences, front-loaded with purpose and disambiguation rationale, then return contents, then policy. Each sentence carries information, though the policy sentence slightly overlaps the usage guidance.

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 no output schema, the description carries the return-value burden and does so (sorted candidates with confidence, motif, competition details, next match). Combined with 100% schema coverage and full annotation set, an agent has what it needs to call it correctly; only pagination/limits are unaddressed.

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 8 parameters including categorie extraction logic and the numero_equipe/fanion distinction. The description reinforces the no-number policy but adds no parameter syntax or format detail beyond the schema. Baseline 3 is appropriate.

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?

States a specific verb+resource ('Recherche et ordonne les équipes candidates d'un club/CTC') with explicit scope and purpose (disambiguation before any calendar/result). It names the sibling ffbb_resolve_team and contrasts its policy, so the agent can distinguish it without opening either 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?

Explicitly says to use it before any calendrier/résultat to disambiguate, and names the alternative `ffbb_resolve_team` along with the differing policy (recommend fanion at 0.85 confidence vs strict guardrail). Both the when and the alternative-selection condition are given.

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