Skip to main content
Glama
kajirita2002

honeycomb-mcp-server

honeycomb_board_get

Retrieve detailed information about a specific board by providing its unique ID within the honeycomb-mcp-server system.

Instructions

Get information about a specific board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardIdYesBoard ID to retrieve

Implementation Reference

  • Handler logic for the honeycomb_board_get tool: extracts boardId from arguments, validates it, calls HoneycombClient.getBoard(boardId), and returns the JSON response.
    case "honeycomb_board_get": {
      const args = request.params.arguments as unknown as BoardGetArgs;
      if (!args.boardId) {
        throw new Error("boardId is required");
      }
      const response = await client.getBoard(args.boardId);
      return {
        content: [{ type: "text", text: JSON.stringify(response) }],
      };
    }
  • Tool definition including name, description, and input schema for honeycomb_board_get, requiring boardId.
    const boardGetTool: Tool = {
      name: "honeycomb_board_get",
      description: "Get information about a specific board. Boards are a place to pin and save useful queries and graphs you want to retain for later reuse and reference.",
      inputSchema: {
        type: "object",
        properties: {
          boardId: {
            type: "string",
            description: "The unique identifier (ID) of a Board.",
          },
        },
        required: ["boardId"],
      },
    };
  • index.ts:784-796 (registration)
    Registration of all tools including boardGetTool (honeycomb_board_get) in the ListToolsRequestHandler response.
    tools: [
      authTool,
      datasetsListTool,
      datasetGetTool,
      columnsListTool,
      queryCreateTool,
      queryGetTool,
      queryResultCreateTool,
      queryResultGetTool,
      datasetDefinitionsListTool,
      boardsListTool,
      boardGetTool,
    ],
  • HoneycombClient.getBoard helper method: performs GET request to /boards/{boardId} API endpoint and returns board information.
    async getBoard(boardId: string): Promise<any> {
      const response = await fetch(`${this.baseUrl}/boards/${boardId}`, {
        method: "GET",
        headers: this.headers,
      });
    
      if (!response.ok) {
        throw new Error(`Failed to get board: ${response.statusText}`);
      }
    
      return await response.json();
    }
  • TypeScript interface defining input arguments for boardGet tool (boardId).
    interface BoardGetArgs {
      boardId: string;
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states 'Get information' which implies a read-only operation, but doesn't specify permissions needed, rate limits, error conditions, or what the return format looks like (e.g., JSON structure). For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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, efficient sentence that front-loads the core purpose ('Get information about a specific board') with zero wasted words. It's appropriately sized for a simple retrieval tool and earns its place by clearly stating the action and target.

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 lack of annotations and output schema, the description is incomplete for a tool that retrieves data. It doesn't explain what information is returned (e.g., board details, metadata), error handling, or how it differs from sibling tools. For a read operation with no structured output documentation, more context is needed to be fully helpful.

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?

Schema description coverage is 100%, with the single parameter 'boardId' clearly documented in the schema as 'Board ID to retrieve'. The description adds no additional meaning beyond this, such as format examples or where to find board IDs. With high schema coverage, the baseline score of 3 is appropriate.

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 action ('Get information') and resource ('about a specific board'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'honeycomb_board_update' or 'honeycomb_boards_list' beyond the basic verb, missing specificity about what type of information is retrieved.

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?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'honeycomb_boards_list' (for listing boards) and 'honeycomb_board_update' (for modifying boards), the description lacks context on prerequisites (e.g., needing a board ID) or exclusions (e.g., not for creating boards).

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

Related 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/kajirita2002/honeycomb-mcp-server'

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