Skip to main content
Glama
idoru

InfluxDB MCP Server

by idoru

create-bucket

Creates a new InfluxDB bucket under an organization, providing a destination for time-series data writes. Specify bucket name, organization ID, and optional retention period.

Instructions

Provision a new bucket under an organization so that subsequent write-data calls have a destination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesFriendly bucket name. Follow InfluxDB naming rules (alphanumeric, dashes, underscores).
orgIDYesOrganization ID (UUID) that will own the bucket. Retrieve it from the organizations resource or create-org output.
retentionPeriodSecondsNoOptional retention duration expressed in seconds. Omit for infinite retention.

Implementation Reference

  • The main handler function `createBucket` that executes the create-bucket tool logic. It accepts name, orgID, and optional retentionPeriodSeconds, then makes a POST request to InfluxDB's /api/v2/buckets endpoint.
    import fetch from "node-fetch";
    import { INFLUXDB_TOKEN, INFLUXDB_URL } from "../config/env.js";
    
    // Tool: Create Bucket
    export async function createBucket({ name, orgID, retentionPeriodSeconds }) {
      console.log(`=== CREATE-BUCKET TOOL CALLED ===`);
      console.log(`Creating bucket: ${name}, orgID: ${orgID}`);
    
      try {
        const bucketData = {
          name,
          orgID,
          retentionRules: retentionPeriodSeconds
            ? [
              { type: "expire", everySeconds: retentionPeriodSeconds },
            ]
            : undefined,
        };
    
        console.log(`Creating bucket with data: ${JSON.stringify(bucketData)}`);
    
        // Use fetch directly instead of our wrapper
        const response = await fetch(`${INFLUXDB_URL}/api/v2/buckets`, {
          method: "POST",
          headers: {
            "Content-Type": "application/json",
            "Authorization": `Token ${INFLUXDB_TOKEN}`,
          },
          body: JSON.stringify(bucketData),
        });
    
        console.log(`Create bucket response status: ${response.status}`);
    
        if (!response.ok) {
          const errorText = await response.text();
          throw new Error(
            `Failed to create bucket: ${response.status} ${errorText}`,
          );
        }
    
        const bucketResponse = await response.json();
    
        console.log(`=== CREATE-BUCKET TOOL COMPLETED SUCCESSFULLY ===`);
        return {
          content: [{
            type: "text",
            text:
              `Bucket created successfully:\nID: ${bucketResponse.id}\nName: ${bucketResponse.name}\nOrganization ID: ${bucketResponse.orgID}`,
          }],
        };
      } catch (error) {
        console.error(`=== CREATE-BUCKET TOOL ERROR: ${error.message} ===`);
        return {
          content: [{
            type: "text",
            text: `Error creating bucket: ${error.message}`,
          }],
          isError: true,
        };
      }
    }
  • src/index.js:120-142 (registration)
    Tool registration using server.tool() with name 'create-bucket', description, Zod schema for parameters (name: string, orgID: string, retentionPeriodSeconds: optional number), and the createBucket handler.
    server.tool(
      "create-bucket",
      "Provision a new bucket under an organization so that subsequent write-data calls have a destination.",
      {
        name: z
          .string()
          .describe(
            "Friendly bucket name. Follow InfluxDB naming rules (alphanumeric, dashes, underscores).",
          ),
        orgID: z
          .string()
          .describe(
            "Organization ID (UUID) that will own the bucket. Retrieve it from the organizations resource or create-org output.",
          ),
        retentionPeriodSeconds: z
          .number()
          .optional()
          .describe(
            "Optional retention duration expressed in seconds. Omit for infinite retention.",
          ),
      },
      createBucket,
    );
  • src/index.js:25-25 (registration)
    Import of the createBucket handler from the handler file into the main server file.
    import { createBucket } from "./handlers/createBucketTool.js";
  • Import of InfluxDB configuration constants (INFLUXDB_TOKEN, INFLUXDB_URL) used to authenticate and address the API endpoint.
    import { INFLUXDB_TOKEN, INFLUXDB_URL } from "../config/env.js";
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 transparency. It does not disclose important traits like permissions required, uniqueness constraints, idempotency, error conditions, or side effects. This is insufficient for an agent to safely invoke the tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, concise and front-loaded. It conveys the essential purpose efficiently, though it could include more detail without becoming verbose.

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 three parameters and no output schema, the description lacks essential context such as uniqueness constraints for bucket names, validity of orgID, potential errors, and return values. This leaves gaps for the agent.

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 coverage is 100%, so the baseline is 3. The description adds minor context by linking the bucket to subsequent write-data calls, but does not significantly enhance understanding beyond the schema descriptions.

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 tool provisions a new bucket under an organization, with a specific verb and resource. It also ties to sibling tools by explaining that this bucket serves as a destination for write-data calls, distinguishing it from create-org, query-data, and write-data.

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 the tool should be used before write-data to create a destination, but does not explicitly state when not to use it or provide alternatives. Usage guidance is present but minimal.

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/idoru/influxdb-mcp-server'

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