Skip to main content
Glama
InfluxDB MCP Server

InfluxDB MCP Server

by idoru

write-data

Inserts newline-delimited line protocol records into an InfluxDB bucket, with optional timestamp precision, so composed telemetry can be written to the database.

Instructions

Stream newline-delimited line protocol records into a bucket. Use this after composing measurements so the LLM can insert real telemetry, optionally controlling timestamp precision. Default org: "my-organization".

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": {
      "bucket": "<bucket>",
      "data": "<data>"
    },
    "name": "write-data"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgNoHuman-readable organization name that owns the destination bucket (the same value returned by the orgs resource). Defaults to "my-organization" if omitted.
dataYesPayload containing one or more line protocol lines (measurements, tags, fields, timestamps) separated by newlines.
bucketYesBucket name to receive the points. Make sure it already exists or call create-bucket first.
precisionNoOptional timestamp precision. Provide it only when the line protocol omits unit suffix context; defaults to nanoseconds.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.4.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / org / description
      Previous value: -"Human-readable organization name that owns the destination bucket (the same value returned by the orgs resource)."New value: +"Human-readable organization name that owns the destination bucket (the same value returned by the orgs resource). Defaults to \"my-organization\" if omitted."
    • changedInput schema / required
      Previous value: -[
      -  "org",
      -  "bucket",
      -  "data"
      -]New value: +[
      +  "bucket",
      +  "data"
      +]
  2. Changed4 schema fields changedv0.2.0
    • changedInput schema / properties / bucket / description
      Previous value: -"The bucket name"New value: +"Bucket name to receive the points. Make sure it already exists or call create-bucket first."
    • changedInput schema / properties / data / description
      Previous value: -"Data in InfluxDB line protocol format"New value: +"Payload containing one or more line protocol lines (measurements, tags, fields, timestamps) separated by newlines."
    • changedInput schema / properties / org / description
      Previous value: -"The organization name"New value: +"Human-readable organization name that owns the destination bucket (the same value returned by the orgs resource)."
    • changedInput schema / properties / precision / description
      Previous value: -"Timestamp precision (ns, us, ms, s)"New value: +"Optional timestamp precision. Provide it only when the line protocol omits unit suffix context; defaults to nanoseconds."
  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, so the description carries the full burden. It conveys that this is a write/ingest path but says nothing about duplicate handling, overwrite semantics, partial-write behavior, batch size limits, or auth requirements — all material for a telemetry ingestion call.

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?

Front-loaded with the core action in the first sentence, followed by sequential guidance. The trailing 'Default org: "my-organization"' repeats the schema and is the one non-earning sentence.

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 the purpose/sequencing is stated, but for a write tool with no annotations and no output schema, nothing is said about failure modes, whether the call is idempotent, or what a successful response looks like.

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 explains bucket, data, org, and precision. The description only adds a light gloss on timestamp precision and restates the default org, which is already in the schema.

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 ('Stream newline-delimited line protocol records into a bucket'), which is unmistakably distinct from sibling tools query-data and create-bucket. It does not explicitly name those siblings, so it lands at 4 rather than 5.

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?

'Use this after composing measurements so the LLM can insert real telemetry' hints at sequencing, and the schema notes the create-bucket prerequisite. There is no explicit when-not guidance or named alternative (e.g., vs. batch import or query-data) in the description itself.

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