Skip to main content
Glama
Sign In
FFBB MCP Server

FFBB MCP Server

by nickdesi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Lecture exacte d'un article de règlement FFBB

ffbb_get_regulation_article
Read-onlyIdempotent

Récupère le texte intégral et exact d'un article spécifique de règlement sans troncature.

Instructions

Récupère le texte intégral et exact d'un article spécifique de règlement sans troncature.

Retourne `dict` avec `document_id`, `article_number`, `titre`, `contenu` et
`saison` ; lecture seule, idempotent, sans effet de bord, cache SWR.
Utilise cet outil quand tu connais le numéro d'article et le document (obtenu via
`ffbb_list_regulations` ou `ffbb_search_regulations`) et que tu veux le contenu
verbatim. Ne pas utiliser pour rechercher par mot-clé — utilise
`ffbb_search_regulations` à la place ; pour lister les documents disponibles —
utilise `ffbb_list_regulations` ; pour expliquer un départage — utilise
`ffbb_explain_tiebreak_rules`. Si `document_id` est omis, précise `organizer`
et `season` pour lever l'ambiguïté.

Input Schema

NameRequiredDescriptionDefault
seasonNoSaison sportive (défaut '2026-2027')2026-2027
organizerNoOrganisateur du texte (ex: 'FFBB', 'Ligue AURA', 'Comité 63')
document_idNoIdentifiant du document source (ex: 'rsg_ffbb_2026_2027', 'rsp_u15_elite_2026_2027', 'reglement_aura_2026_2027', 'reglement_comite_63_2026_2027')
article_numberYesNuméro ou référence de l'article (ex: 'Article 28', 'Article 51', 'Article 4.1', 'Article 7')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.13.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description partly restates them ('lecture seule, idempotent, sans effet de bord'), which earns no extra credit. It does add genuine context beyond the annotations: the no-truncation guarantee, the returned dict fields, and SWR caching behavior.

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?

Front-loaded with the verb and the no-truncation promise, then return shape, then routing. Efficient, though the safety restatement ('sans effet de bord') is mild redundancy against the annotations.

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?

No output schema exists, and the description compensates by enumerating the returned dict keys. Combined with the explicit alternative-tool routing and the ambiguity-resolution rule, an agent has everything needed to call this correctly.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real routing semantics: when document_id is omitted the caller must supply organizer and season to disambiguate. That is decision-relevant information the schema alone does not convey.

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 and resource ('récupère le texte intégral et exact d'un article spécifique de règlement') plus the key differentiator 'sans troncature'. An agent can distinguish it from the search/list siblings without opening any 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 gives the when condition (article number known, document obtained via ffbb_list_regulations or ffbb_search_regulations) and names three alternatives by exact tool name with the condition that selects each. Also covers the fallback case when document_id is omitted.

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