The FFBB MCP server provides 2 tools with mixed quality. Naming is action-oriented (ffbb_search, ffbb_version) and follows verb_noun convention. Both tools have substantial descriptions that explain purpose and use cases. However, the schema documentation is incomplete, while ffbb_search has enumerated type constraints and detailed parameter descriptions, the input parameter objects lack explicit JSON Schema type declarations visible in the source. ffbb_version declares an empty input object {} with no parameters, which is correct but minimal. The ffbb_search tool demonstrates good constraint design with enum values ('all', 'competitions', 'organismes', etc.) and descriptive parameter guidance. Error handling and output schemas are not visible in the provided code excerpts, which limits assessment of recovery guidance and structured output practices. The server includes tool annotations (readOnlyHint) for both tools, indicating awareness of current MCP patterns, but overall schema rigor could be stronger.

• Document output schemas for both tools. ffbb_version should declare return type as {package_version: str, mcp_sdk_version: str, python_version: str, transport: str, cache_ttls: dict}. ffbb_search should document structure of search results (array of objects with fields like id, name, type, etc.) and whether results are paginated.
• Add min/max constraints to ffbb_search 'limit' parameter: 'Nombre maximal de résultats (1 - 100, défaut: 20)' to prevent runaway queries.
• Expand ffbb_search 'filter_by' description with Meilisearch syntax examples: 'Filtre optionnel Meilisearch (ex: "region = \'Auvergne\'" ou "niveau > 18"). Consulter la documentation Meilisearch pour la syntaxe complète.'
• Implement and document error handling for ffbb_search: clarify what happens on empty results, invalid 'type' enum, Meilisearch timeout, or network failure. Include recovery guidance (e.g., 'No results found for query. Try broadening search terms or use ffbb_list_* for discovery.').
• Verify that ffbb_search output includes IDs/keys (e.g., competition_id, club_id) that downstream tools (ffbb_club, ffbb_bilan) accept, enabling agents to chain calls without extra lookups.
• Add parameter bounds and descriptions: clarify 'query' length limits, 'type' enum semantics, and whether 'filter_by' is optional (nullable).

Inferred effective spec: 2026-07-28+.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry