Skip to main content
Glama
idoru

InfluxDB MCP Server

by idoru

query-data

Execute Flux queries on InfluxDB time-series databases to retrieve and analyze data. Specify the organization and query string to fetch precise time-series insights.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orgYesThe organization name
queryYesFlux query string

Implementation Reference

  • The main handler function for the 'query-data' tool. It makes a POST request to InfluxDB's /api/v2/query endpoint with the provided organization and Flux query, returns the response as annotated CSV text, or an error message if the query fails.
    export async function queryData({ org, query }) {
      try {
        const response = await influxRequest(
          `/api/v2/query?org=${encodeURIComponent(org)}`,
          {
            method: "POST",
            body: JSON.stringify({ query, type: "flux" }),
          },
        );
    
        const responseText = await response.text();
    
        return {
          content: [{
            type: "text",
            text: responseText,
          }],
        };
      } catch (error) {
        return {
          content: [{
            type: "text",
            text: `Error executing query: ${error.message}`,
          }],
          isError: true,
        };
      }
    }
  • src/index.js:103-119 (registration)
    Registers the 'query-data' tool with the MCP server, including the tool name, description, Zod input schema for 'org' and 'query' parameters, and binds it to the queryData handler function.
    server.tool(
      "query-data",
      "Execute a Flux query inside an organization to inspect measurement schemas, run aggregations, or validate recently written data.",
      {
        org: z
          .string()
          .describe(
            "Organization whose buckets the query should target (exact name, not ID).",
          ),
        query: z
          .string()
          .describe(
            "Flux query text. Multi-line strings are supported; results are returned as annotated CSV for easy parsing.",
          ),
      },
      queryData,
    );
  • Zod schema defining the input parameters for the 'query-data' tool: 'org' (string) and 'query' (string) with descriptions.
      org: z
        .string()
        .describe(
          "Organization whose buckets the query should target (exact name, not ID).",
        ),
      query: z
        .string()
        .describe(
          "Flux query text. Multi-line strings are supported; results are returned as annotated CSV for easy parsing.",
        ),
    },
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/idoru/influxdb-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server