Skip to main content
Glama
InfluxDB MCP Server

InfluxDB MCP Server

by Quorralyne

create_database

Create a new InfluxDB database with a valid name and optional Cloud Dedicated settings for tables, retention, and columns.

Instructions

Create a new database in InfluxDB. Database names must follow InfluxDB naming rules: alphanumeric characters, dashes (-), underscores (_), and forward slashes (/) are allowed. Must start with a letter or number. Maximum 64 characters. For Cloud Dedicated, optional configuration parameters can be specified.

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>"
    },
    "name": "create_database"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the database to create (alphanumeric, -, _, / allowed; max 64 chars; must start with letter/number)
maxTablesNoMaximum number of tables (Cloud Dedicated only, default: 500)
retentionPeriodNoRetention period in nanoseconds (Cloud Dedicated only, default: 0 = no expiration)
maxColumnsPerTableNoMaximum columns per table (Cloud Dedicated only, default: 200)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full behavioral burden and partially meets it by disclosing naming rules, the 64-character cap, and that configuration parameters only apply to Cloud Dedicated. It omits important mutation behavior: what happens if a database of the same name already exists, required permissions, and whether creation is reversible or billable.

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?

Three short sentences, front-loaded with the action and followed by the constraint that most affects a caller. The naming-rules sentence partially duplicates the schema pattern and maxLength, which is minor waste but not harmful.

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?

Parameter coverage is complete via the schema, but for a mutating create operation with no annotations and no output schema, the description never states what is returned (e.g., the created database object) or how failures such as duplicate names surface. It is minimally adequate rather than 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 the schema already documents all four parameters including defaults and minimums, which sets the baseline at 3. The description restates the name pattern already encoded in the schema regex and adds only the Cloud Dedicated applicability note, so it contributes little new meaning.

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 opens with a specific verb and resource ("Create a new database in InfluxDB"), which cleanly distinguishes it from delete_database, update_database, and list_databases among the siblings. It does not explicitly name an alternative tool, so it falls short of the top band, but the intent is unambiguous.

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?

Usage is only implied by the create verb; there is no explicit statement of when to use this versus other lifecycle tools, and no prerequisites are given. The one conditional hint, "For Cloud Dedicated, optional configuration parameters can be specified," is useful context but is about parameter applicability rather than when-to-use guidance.

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