Skip to main content
Glama
honeycombio
by honeycombio

get_board

Retrieve a specific dashboard from Honeycomb observability data to access its ID, name, description, and timestamps for analysis.

Instructions

Retrieves a specific board (dashboard) from a Honeycomb environment. This tool returns a detailed object containing the board's ID, name, description, creation time, and last update time.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
environmentYesThe Honeycomb environment
boardIdYesThe ID of the board to retrieve

Implementation Reference

  • The async handler function for the 'get_board' tool. Validates environment and boardId parameters, fetches the board using HoneycombAPI.getBoard, formats the response as MCP content with metadata, and handles errors.
    handler: async ({ environment, boardId }: z.infer<typeof GetBoardSchema>) => {
      // Validate input parameters
      if (!environment) {
        return handleToolError(new Error("environment parameter is required"), "get_board");
      }
      
      if (!boardId) {
        return handleToolError(new Error("boardId parameter is required"), "get_board");
      }
    
      try {
        // Fetch board from the API
        const board = await api.getBoard(environment, boardId);
        
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(board, null, 2),
            },
          ],
          metadata: {
            environment,
            boardId,
            name: board.name
          }
        };
      } catch (error) {
        return handleToolError(error, "get_board");
      }
    }
  • Zod schema defining the input parameters for the get_board tool: required environment (string) and boardId (string).
    export const GetBoardSchema = z.object({
      environment: z.string().min(1).trim().describe("The Honeycomb environment"),
      boardId: z.string().min(1).trim().describe("The ID of the board to retrieve"),
    }).describe("Parameters for retrieving a specific Honeycomb board with all its queries and visualizations.");
  • The get_board tool is instantiated via createGetBoardTool(api) and added to the array of tools that are registered with the MCP server in the registerTools function.
    createGetBoardTool(api),
Behavior3/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 discloses that the tool returns a detailed object with specific fields (ID, name, description, creation time, last update time), which helps understand the return format. However, it doesn't mention error conditions, authentication needs, rate limits, or whether it's a read-only operation (though 'retrieves' implies reading).

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 two concise sentences that are front-loaded with the core purpose and follow with return value details. Every sentence adds value without redundancy, making it efficient and well-structured.

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

Completeness4/5

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

Given the tool's low complexity (2 simple parameters, no output schema, no annotations), the description is fairly complete. It covers the purpose, return object structure, and distinguishes from siblings. However, it could improve by mentioning authentication or error handling, but for a simple retrieval tool, it's mostly adequate.

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%, so the schema already documents both parameters ('environment' and 'boardId') adequately. The description doesn't add any additional parameter semantics beyond what the schema provides, such as format examples or constraints, so it meets the baseline for high schema coverage.

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

Purpose5/5

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

The description clearly states the specific action ('Retrieves'), resource ('a specific board (dashboard)'), and context ('from a Honeycomb environment'). It distinguishes from sibling tools like 'list_boards' by specifying retrieval of a single board rather than listing multiple boards.

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 when a specific board needs to be retrieved, but doesn't explicitly state when to use this tool versus alternatives like 'list_boards' for multiple boards or other sibling tools for different resources. No explicit exclusions or prerequisites are mentioned.

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/honeycombio/honeycomb-mcp'

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