Skip to main content
Glama
kajirita2002

honeycomb-mcp-server

honeycomb_boards_list

Retrieve a list of all available boards from the honeycomb-mcp-server to manage or analyze system configurations efficiently.

Instructions

List all boards

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the honeycomb_boards_list tool. Dispatches to client.listBoards() and formats the response as MCP content.
    case "honeycomb_boards_list": {
      const response = await client.listBoards();
      return {
        content: [{ type: "text", text: JSON.stringify(response) }],
      };
    }
  • Tool schema definition including name, description, and empty input schema for honeycomb_boards_list.
    const boardsListTool: Tool = {
      name: "honeycomb_boards_list",
      description: "List all boards. 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: {},
      },
    };
  • index.ts:782-798 (registration)
    Registration of boardsListTool in the list of tools exposed via ListToolsRequestSchema.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [
          authTool,
          datasetsListTool,
          datasetGetTool,
          columnsListTool,
          queryCreateTool,
          queryGetTool,
          queryResultCreateTool,
          queryResultGetTool,
          datasetDefinitionsListTool,
          boardsListTool,
          boardGetTool,
        ],
      };
    });
  • HoneycombClient.listBoards() method that performs the API call to list boards.
    async listBoards(): Promise<any> {
      const response = await fetch(`${this.baseUrl}/boards`, {
        method: "GET",
        headers: this.headers,
      });
    
      if (!response.ok) {
        throw new Error(`Failed to list boards: ${response.statusText}`);
      }
    
      return await response.json();
    }
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. 'List all boards' implies a read-only operation that returns multiple items, but it doesn't specify whether this requires authentication, how results are paginated or formatted, or if there are any rate limits. This leaves significant gaps for an AI agent to understand the tool's 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 'List all boards' is extremely concise—just three words—and front-loaded with the core action. There is no wasted language, making it efficient for quick understanding without unnecessary detail.

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 list operation. It doesn't explain what 'boards' are in this context (e.g., Honeycomb data visualization boards), how results are returned, or any prerequisites like authentication. For a tool with no structured support, 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.

Parameters4/5

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

The tool has 0 parameters, and the input schema has 100% description coverage (though empty). The description doesn't need to add parameter semantics since there are no parameters, so it meets the baseline expectation. No additional value is required beyond stating the action.

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 'List all boards' clearly states the verb ('List') and resource ('boards'), making the purpose immediately understandable. However, it doesn't distinguish this tool from other list tools like honeycomb_columns_list or honeycomb_markers_list, which have similar naming patterns for different resources.

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. With sibling tools like honeycomb_board_get (for a specific board) and honeycomb_board_create (for creating boards), there's no indication of when listing all boards is appropriate versus retrieving a single board or creating a new one.

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