Skip to main content
Glama
InfluxDB MCP Server

InfluxDB MCP Server

by idoru

create-org

Create an InfluxDB organization to isolate users or projects before adding buckets and tokens.

Instructions

Create a brand-new organization to isolate users or projects before generating buckets and tokens.

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-org"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesDisplay name for the organization as it should appear in InfluxDB Cloud/OSS.
descriptionNoOptional free-form description that helps humans understand why the org exists.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed2 schema fields changedv0.2.0
    • changedInput schema / properties / description / description
      Previous value: -"Organization description (optional)"New value: +"Optional free-form description that helps humans understand why the org exists."
    • changedInput schema / properties / name / description
      Previous value: -"The organization name"New value: +"Display name for the organization as it should appear in InfluxDB Cloud/OSS."
  3. First observedv1.0.0

TDQS

B3.2/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. Beyond 'brand-new' implying a mutation, it says nothing about permissions required, whether the call is idempotent, what happens on duplicate names, or what the response contains — significant gaps for a create operation.

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?

A single front-loaded sentence with no filler. It is efficient, though its brevity is partly why behavioral gaps remain rather than a model of well-packed information.

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?

Parameters are fully covered by the schema and there is no output schema to explain, but as an unannotated mutation tool the description should say more about side effects, required auth, and what is returned. 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 coverage is 100% with only two well-documented parameters, so the schema already explains both 'name' and 'description'. The description adds no additional meaning about parameter formatting or defaults, 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 ('Create a brand-new organization') and adds the reason for doing so (isolating users/projects). It does not explicitly name the sibling tools it differs from, but the mention of buckets and tokens makes the relationship to create-bucket clear enough.

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?

'...before generating buckets and tokens' gives a sequencing hint that this is a prerequisite step in a workflow. However, there is no explicit when-to-use/when-not guidance, no statement about what to do if an org already exists, and no alternative tools named.

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