Skip to main content
Glama
InfluxDB MCP Server

InfluxDB MCP Server

by idoru

query-data

Execute Flux queries to inspect measurement schemas, run aggregations, or validate recently written data in an InfluxDB organization.

Instructions

Execute a Flux query inside an organization to inspect measurement schemas, run aggregations, or validate recently written data. 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": {
      "query": "<query>"
    },
    "name": "query-data"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgNoOrganization whose buckets the query should target (exact name, not ID). Defaults to "my-organization" if omitted.
queryYesFlux query text. Multi-line strings are supported; results are returned as annotated CSV for easy parsing.

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: -"Organization whose buckets the query should target (exact name, not ID)."New value: +"Organization whose buckets the query should target (exact name, not ID). Defaults to \"my-organization\" if omitted."
    • changedInput schema / required
      Previous value: -[
      -  "org",
      -  "query"
      -]New value: +[
      +  "query"
      +]
  2. Changed2 schema fields changedv0.2.0
    • changedInput schema / properties / org / description
      Previous value: -"The organization name"New value: +"Organization whose buckets the query should target (exact name, not ID)."
    • changedInput schema / properties / query / description
      Previous value: -"Flux query string"New value: +"Flux query text. Multi-line strings are supported; results are returned as annotated CSV for easy parsing."
  3. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/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. It implies read-oriented use through verbs like "inspect" and "validate" and discloses the default organization, but it does not explicitly confirm read-only behavior, permissions requirements, side-effect boundaries, or error behavior for Flux queries.

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?

The description is two tight sentences, front-loads the core action and use cases, and includes the default organization without unnecessary detail. Every sentence contributes relevant information.

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

Completeness4/5

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

Given the simple two-parameter schema and absence of an output schema, the description covers the tool's purpose and default org well. It could more explicitly mention result format or permission expectations, but it is largely complete for an agent to select and invoke the tool.

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 both the org and query parameters are already documented in the input schema. The description reinforces the default org value but adds no meaningful syntax, constraints, or semantics beyond what the schema already provides, making the baseline 3 appropriate.

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 states a specific verb and resource ("Execute a Flux query") and lists concrete use cases: inspecting measurement schemas, running aggregations, and validating recently written data. It is clearly a query/read tool, distinct from the sibling create-bucket, write-data, and create-org tools, though it does not explicitly name or contrast those alternatives.

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 description provides clear usage contexts: inspect schemas, run aggregations, or validate data. It does not state when not to use the tool or explicitly compare it to alternatives, but the intended scenarios are sufficiently clear for an agent.

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