Skip to main content
Glama
InfluxDB MCP Server

InfluxDB MCP Server

by idoru

create-bucket

Provisions a new bucket under a specified organization, giving write-data calls a destination and supporting optional retention settings.

Instructions

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "orgID": "<orgID>"
    },
    "name": "create-bucket"
  }
}

Input 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 whole seconds. Omit (or pass 0) for infinite retention.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.4.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / retentionPeriodSeconds / description
      Previous value: -"Optional retention duration expressed in seconds. Omit for infinite retention."New value: +"Optional retention duration expressed in whole seconds. Omit (or pass 0) for infinite retention."
    • addedInput schema / properties / retentionPeriodSeconds / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / retentionPeriodSeconds / minimum
      Added value: +0
    • changedInput schema / properties / retentionPeriodSeconds / type
      Previous value: -"number"New value: +"integer"
  2. Changed3 schema fields changedv0.2.0
    • changedInput schema / properties / name / description
      Previous value: -"The bucket name"New value: +"Friendly bucket name. Follow InfluxDB naming rules (alphanumeric, dashes, underscores)."
    • changedInput schema / properties / orgID / description
      Previous value: -"The organization ID"New value: +"Organization ID (UUID) that will own the bucket. Retrieve it from the organizations resource or create-org output."
    • changedInput schema / properties / retentionPeriodSeconds / description
      Previous value: -"Retention period in seconds (optional)"New value: +"Optional retention duration expressed in seconds. Omit for infinite retention."
  3. First observedv1.0.0

TDQS

A3.5/5.0
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 behavioral burden, yet it discloses nothing about whether creation is idempotent, what happens when the name collides, required permissions, or what the response contains. For a mutation tool with zero annotation coverage this is a significant gap.

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?

A single front-loaded sentence with zero filler, stating the action, scope, and downstream purpose in order of importance.

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

Completeness3/5

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

With only three parameters and full schema coverage, the input side is well served, and the purpose is clear. However, with no annotations and no output schema, the description should say more about mutation semantics (idempotency, conflicts, auth) to be truly complete.

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 all three parameters (name, orgID, retentionPeriodSeconds) are already documented in the schema. The description adds no parameter-level meaning such as default retention behavior or naming constraints beyond what the schema states, so the baseline 3 applies.

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?

States a specific verb and resource ('Provision a new bucket') and scopes it to an organization, plus ties it to the write-data sibling as the downstream consumer. It is clearly distinguishable from create-org and query-data, though it never explicitly contrasts itself with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'so that subsequent write-data calls have a destination' gives a clear precondition: create this before writing data. It implies the context of use well but offers no explicit exclusions or alternative paths (e.g., what to do if a bucket already exists).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools