Skip to main content
Glama

get_boards

Retrieve a list of all Canny boards accessible with your current API key to manage customer feedback platforms.

Instructions

List all Canny boards accessible with the current API key

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Definition of the get_boards tool including its handler function that fetches and formats the list of Canny boards.
    export const getBoardsTool = {
      name: 'get_boards',
      description: 'List all Canny boards accessible with the current API key',
      inputSchema: {
        type: 'object',
        properties: {},
        additionalProperties: false,
      },
      handler: async (args: unknown, client: CannyClient) => {
        validateToolInput<GetBoardsInput>(args, GetBoardsSchema);
        
        const response = await client.getBoards();
        
        if (response.error) {
          throw new Error(`Failed to fetch boards: ${response.error}`);
        }
    
        if (!response.data || response.data.length === 0) {
          return 'No boards found or you do not have access to any boards.';
        }
    
        const boards = response.data.map(board => ({
          id: board.id,
          name: board.name,
          url: board.url,
          postCount: board.postCount,
          isPrivate: board.isPrivate,
        }));
    
        return `Found ${boards.length} board(s):\n\n${boards
          .map(board => 
            `**${board.name}** (ID: ${board.id})\n` +
            `  - URL: ${board.url}\n` +
            `  - Posts: ${board.postCount}\n` +
            `  - Private: ${board.isPrivate ? 'Yes' : 'No'}\n`
          )
          .join('\n')}`;
      },
    };
  • Zod schema for validating get_boards tool input (no parameters required).
    const GetBoardsSchema = z.object({});
  • Registration of the getBoardsTool in the main tools array for MCP.
    export const tools: Tool[] = [
      // Board management
      getBoardsTool,
      
      // Post management
      getPostsTool,
      getPostTool,
      searchPostsTool,
      createPostTool,
      updatePostTool,
    
      // Extended functionality - temporarily disabled for debugging
      // getCategoresTool,
      // getCommentsTool,
      // getUsersTool,
      // getTagsTool,
    ];
  • The CannyClient.getBoards() method called by the tool handler to fetch boards from the API.
    /**
     * Get all boards accessible to the API key
     */
    async getBoards(): Promise<CannyApiResponse<CannyBoard[]>> {
      const response = await this.makeRequest<{ boards: CannyBoard[] }>({
        method: 'GET',
        url: '/boards/list',
      });
    
      // Handle the nested response structure
      if (response.data && response.data.boards) {
        return {
          data: response.data.boards,
          status: response.status,
        };
      }
    
      return {
        data: [],
        status: response.status,
        error: response.error,
      };
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden. It mentions the scope ('all Canny boards') and access constraint ('accessible with the current API key'), which adds some behavioral context. However, it lacks details on rate limits, pagination, error handling, or response format, which are important for a list operation.

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?

The description is a single, clear sentence that efficiently conveys the tool's purpose without any wasted words. It is front-loaded with the main action and resource, making it easy to parse and understand quickly.

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

Completeness3/5

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

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is adequate but has gaps. It covers the basic purpose and access scope, but without annotations or output schema, it misses behavioral details like response structure or limitations, which could help the agent use it 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?

The tool has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description appropriately doesn't add parameter details, and the baseline for 0 parameters is 4, as it avoids unnecessary information.

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

Purpose4/5

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

The description clearly states the verb ('List') and resource ('all Canny boards'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_posts' or 'search_posts', which might also list resources but for different entities.

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

Usage Guidelines3/5

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

The description implies usage context by specifying 'accessible with the current API key', suggesting it's for retrieving accessible boards. However, it provides no explicit guidance on when to use this tool versus alternatives like 'get_posts' or 'search_posts', leaving the agent to infer based on resource type.

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/itsocialist/canny-mcp-server'

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