Skip to main content
Glama

get-boards

Retrieve all Trello boards from your account to view and manage your projects and workflows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'get_boards' tool. It retrieves the board service from the factory and calls getBoards with the provided arguments.
    get_boards: async (args: any) => {
        const boardService = ServiceFactory.getInstance().getBoardService();
        return boardService.getBoards(args);
    },
  • The schema definition for the 'get_boards' tool, including name, description, and input validation schema.
        name: "get_boards",
        description: "Retrieve a list of boards for the authenticated user. Use this tool to get an overview of available boards or to search for specific ones using filters.",
        inputSchema: {
            type: "object",
            properties: {
                filter: {
                    type: "string",
                    enum: ["all", "closed", "members", "open", "organization", "public", "starred", "unpinned"],
                    description: "Filter boards by status or membership"
                },
                fields: {
                    type: "array",
                    items: { type: "string" },
                    description: "Specific fields to include in the response (default: all fields)"
                }
            }
        }
    },
  • src/index.ts:97-101 (registration)
    Registration of the list tools request handler in the MCP server, which returns all tools including 'get_boards' via the trelloTools array.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
        return {
            tools: trelloTools
        };
    });
  • src/index.ts:125-140 (registration)
    Registration of the call tool request handler in the MCP server, which dispatches to the specific handler for 'get_boards' using trelloToolHandlers.
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
        try {
            const toolName = request.params.name;
            // Use type assertion to tell TypeScript that toolName is a valid key
            const handler = trelloToolHandlers[toolName as keyof typeof trelloToolHandlers];
    
            if (!handler) {
                throw new McpError(
                    ErrorCode.MethodNotFound,
                    `Unknown tool: ${toolName}`
                );
            }
    
            // Execute the tool handler with the provided arguments
            const result = await handler(request.params.arguments);
  • The underlying board service method called by the get_boards handler. (Note: excerpt abbreviated as full implementation not read.)
    /**
     * Creates a new BoardService instance
     * @param trelloService - The TrelloService instance
     */
    constructor(trelloService: TrelloService) {
        this.trelloService = trelloService;
    }
    
    /**
     * Get all boards for the authenticated user
     * @param filters - Optional filters to apply
     * @returns Promise resolving to an array of boards
     */
    async getBoards(filters?: BoardFilters): Promise<TrelloBoard[]> {
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

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

Parameters1/5

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

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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/v4lheru/trello-mcp-server'

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