trello_list_boards
Retrieve a list of all open Trello boards for the authenticated user.
Instructions
Elenca tutte le board Trello aperte dell'utente
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Retrieve a list of all open Trello boards for the authenticated user.
Elenca tutte le board Trello aperte dell'utente
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds that only 'open' boards are listed, which is useful. Annotations already indicate read-only behavior. No additional behavioral details like pagination or ordering are provided.
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, clear sentence that conveys the tool's purpose without extraneous words. Perfectly concise.
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?
For a simple list operation with no parameters and no output schema, the description provides sufficient context to understand what the tool does and what it returns.
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?
No parameters exist, so schema coverage is 100%. The description adds no parameter information, which is acceptable for a parameterless tool.
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?
The description specifies the verb 'list', the resource 'boards', and the scope 'open'. It clearly distinguishes from siblings like trello_get_board_overview which focuses on a single board.
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 implies usage for listing open boards but does not explicitly state when not to use it or compare with alternatives. However, the purpose is clear enough to differentiate from other tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/imanagerpms/trelloAI'
If you have feedback or need assistance with the MCP directory API, please join our Discord server