Skip to main content
Glama
nickdesi

FFBB MCP Server

by nickdesi

Ressource FFBB par identifiant

ffbb_get
Read-onlyIdempotent

Retrieve French Basketball Federation (FFBB) resources by ID: competition, poule (standings and matches), club, officials, and coaches. Optionally force cache bypass for live poule scores.

Instructions

Recupere une ressource FFBB par identifiant.

- `type="competition"` equivaut a `get_competition`.
- `type="poule"` charge la poule (classements + rencontres).
- `type="organisme"` charge les details d'un club.

⚠️ Attention: `type="poule"` peut être tronqué si la poule est grande.
Pour un calendrier exhaustif, préférez `ffbb_club(action="calendrier")`.

Avertissement: ne pas utiliser pour obtenir un score ou un prochain match.
Utiliser `ffbb_last_result` et `ffbb_next_match` a la place.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesIdentifiant numerique de la ressource FFBB.
typeYesType de ressource a charger.
force_refreshNoSi True et type='poule', contourne le cache pour recuperer la poule en temps reel (scores live).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Adds critical behavioral context beyond annotations: truncation warning for 'poule' type, force_refresh parameter effect, and safe reading behavior. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Concise yet comprehensive, with a top-level summary, bullet-point details for types, and warnings. Every sentence is purposeful and well-organized.

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?

Given the tool's complexity (multiple types, warnings, alternatives) and presence of an output schema, the description covers all necessary context for correct selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions for all three parameters, and the description adds extra meaning by mapping type values to other tools and explaining force_refresh's real-time caching behavior.

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?

The description clearly states 'Recupere une ressource FFBB par identifiant' and differentiates from sibling tools by mapping types to equivalent specialized tools and warning against use for scores/next match.

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 provides when to use (fetching resource by id), when not to use (scores/next match), and alternatives (ffbb_last_result, ffbb_next_match, ffbb_club).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nickdesi/FFBB-MCP-Server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server