Skip to main content
Glama

get_board

Retrieve comprehensive board details including columns and property definitions to manage tasks and workflows in Focalboard.

Instructions

Get detailed information about a specific board, including all its columns and property definitions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardIdYesThe ID of the board to retrieve

Implementation Reference

  • src/index.ts:46-59 (registration)
    Registration of the 'get_board' MCP tool, including its name, description, and input schema definition.
    {
      name: 'get_board',
      description: 'Get detailed information about a specific board, including all its columns and property definitions.',
      inputSchema: {
        type: 'object',
        properties: {
          boardId: {
            type: 'string',
            description: 'The ID of the board to retrieve'
          }
        },
        required: ['boardId']
      }
    },
  • MCP server request handler for the 'get_board' tool: parses input arguments, validates boardId, calls FocalboardClient.getBoard, and returns the result as formatted JSON text content.
    case 'get_board': {
      const boardId = args?.boardId as string;
      if (!boardId) {
        throw new Error('boardId is required');
      }
      const board = await focalboard.getBoard(boardId);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(board, null, 2)
          }
        ]
      };
    }
  • Implementation of the getBoard method in FocalboardClient: performs an authenticated GET request to the Focalboard API endpoint /boards/{boardId} to fetch the board details.
    async getBoard(boardId: string): Promise<Board> {
      return this.makeRequest<Board>(`/boards/${boardId}`);
    }
  • TypeScript interface defining the Board structure, which represents the output data type returned by the get_board tool.
    export interface Board {
      id: string;
      teamId: string;
      channelId: string;
      createdBy: string;
      modifiedBy: string;
      type: string; // 'O' (open) or 'P' (private)
      minimumRole: string;
      title: string;
      description: string;
      icon: string;
      showDescription: boolean;
      isTemplate: boolean;
      templateVersion: number;
      properties: Record<string, any>;
      cardProperties: PropertyTemplate[];
      createAt: number;
      updateAt: number;
      deleteAt: number;
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves detailed information, implying a read-only operation, but doesn't cover critical aspects like authentication requirements, error handling (e.g., invalid board IDs), rate limits, or response format. For a tool with no annotations, this leaves significant behavioral gaps.

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, well-structured sentence that efficiently conveys the core functionality without redundancy. It front-loads the key action ('Get detailed information') and specifies inclusions ('columns and property definitions'), making every word count. There is no wasted text or unnecessary elaboration.

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

Completeness2/5

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

Given the tool's complexity (retrieving detailed board data), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what 'detailed information' entails beyond columns and properties, how errors are handled, or the response structure. For a read operation with no structured output documentation, more context is needed to guide the agent effectively.

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

Parameters3/5

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

The input schema has 100% description coverage, with the 'boardId' parameter clearly documented. The description adds no additional parameter semantics beyond what the schema provides (e.g., no examples of board ID formats or constraints). According to the rules, with high schema coverage (>80%), the baseline is 3 even without extra param info in the description.

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 tool's purpose with a specific verb ('Get') and resource ('board'), specifying what information is retrieved ('detailed information about a specific board, including all its columns and property definitions'). It distinguishes from siblings like 'list_boards' (which lists boards) and 'get_card' (which retrieves cards), though it doesn't explicitly mention these distinctions. The purpose is unambiguous but lacks explicit sibling differentiation.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a board ID), contrast with 'list_boards' for browsing boards or 'get_cards' for board contents, or specify use cases. The agent must infer usage from context alone, which is insufficient for clear decision-making.

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/gmjuhasz/focalboard-mcp-server'

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