Skip to main content
Glama
kajirita2002

honeycomb-mcp-server

honeycomb_columns_list

Retrieve a complete list of columns for a specified dataset using the provided dataset slug to streamline data analysis and organization.

Instructions

List all columns in a dataset

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
datasetSlugYesDataset slug to list columns for

Implementation Reference

  • MCP tool handler for honeycomb_columns_list: extracts and validates arguments, calls HoneycombClient.listColumns, formats and returns the JSON response.
    case "honeycomb_columns_list": {
      const args = request.params.arguments as unknown as ColumnListArgs;
      if (!args.datasetSlug) {
        throw new Error("datasetSlug is required");
      }
      const response = await client.listColumns(args.datasetSlug, args.key_name);
      return {
        content: [{ type: "text", text: JSON.stringify(response) }],
      };
    }
  • Defines the tool metadata, description, and input schema (datasetSlug required, key_name optional) for honeycomb_columns_list.
    const columnsListTool: Tool = {
      name: "honeycomb_columns_list",
      description: "List all columns in a dataset. Columns are fields in the events you send to Honeycomb.",
      inputSchema: {
        type: "object",
        properties: {
          datasetSlug: {
            type: "string",
            description: "The dataset slug.",
          },
          key_name: {
            type: "string",
            description: "Optional: Filter columns by a specific name.",
          },
        },
        required: ["datasetSlug"],
      },
    };
  • index.ts:784-798 (registration)
    Registers the honeycomb_columns_list tool (as columnsListTool) in the list returned by ListToolsRequestHandler.
        tools: [
          authTool,
          datasetsListTool,
          datasetGetTool,
          columnsListTool,
          queryCreateTool,
          queryGetTool,
          queryResultCreateTool,
          queryResultGetTool,
          datasetDefinitionsListTool,
          boardsListTool,
          boardGetTool,
        ],
      };
    });
  • HoneycombClient helper method: constructs API URL for /columns/{datasetSlug}?key_name={key_name}, performs GET request, returns parsed JSON.
    async listColumns(datasetSlug: string, keyName?: string): Promise<any> {
      let url = `${this.baseUrl}/columns/${datasetSlug}`;
      
      // key_nameパラメータが指定されている場合、URLクエリに追加
      if (keyName) {
        url += `?key_name=${encodeURIComponent(keyName)}`;
      }
      
      const response = await fetch(url, {
        method: "GET",
        headers: this.headers,
      });
    
      if (!response.ok) {
        throw new Error(`Failed to list columns: ${response.statusText}`);
      }
    
      return await response.json();
    }
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 of behavioral disclosure. It states it's a list operation, implying read-only behavior, but doesn't cover aspects like pagination, rate limits, error handling, or the format of returned data, leaving gaps in understanding how the tool behaves.

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 directly states the tool's purpose without unnecessary words. It's front-loaded and wastes no space, making it easy to parse quickly.

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. It doesn't explain what the list output includes (e.g., column names, types), potential constraints, or how to interpret results, which is insufficient for a tool that likely returns structured data.

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 'datasetSlug' clearly documented. The description adds no additional parameter details beyond what the schema provides, so it meets the baseline score of 3 for high schema coverage without extra value.

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 ('List') and resource ('columns in a dataset'), making the purpose understandable. However, it doesn't distinguish this from sibling tools like 'honeycomb_dataset_get' or 'honeycomb_datasets_list', which operate on different resources but share similar listing patterns.

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. For example, it doesn't mention if this is for metadata exploration, query preparation, or other contexts, nor does it reference sibling tools that might serve related purposes.

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