list_leaguesRetrieve every Kickbase league linked to an account, including ID, name, budget, and user count, so you can review and manage league participation.
List all Kickbase leagues the account is in (id, name, budget, users).
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden, and "List" does at least signal a non-mutating read. However, it says nothing about authentication/account binding (implicit in "the account is in"), whether results are paginated, what an empty account returns, or error behavior when no token is present.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with the verb and scope first and the returned fields in parentheses. No filler, nothing to trim.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With zero parameters and an output schema present, the description only needs to establish scope and purpose, which it does. The parenthetical field list is arguably redundant with the output schema, but nothing essential is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so there is nothing to disambiguate and the baseline is a 4. The description correctly implies no input is needed by framing the result as purely account-scoped.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
"List all Kickbase leagues the account is in" gives a specific verb (list) and a scoped resource (leagues the authenticated account belongs to), plus the fields returned. It contrasts by scope with siblings like get_league_overview and get_league_ranking, though it never names them, so the differentiation is implicit rather than explicit.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description never states when to use this tool versus get_league_overview, get_league_ranking, or the other league-scoped siblings, nor does it mention that the returned IDs are a prerequisite for those calls. The account-wide scope hints at a discovery use case, but the agent has to infer that.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.