Skip to main content
Glama
bastiaan365

mcp-it-ops

by bastiaan365

query_influxdb_flux

Run custom Flux queries on InfluxDB to retrieve and parse time-series records for IT operations monitoring.

Instructions

Execute a Flux query against the local InfluxDB and return parsed records.

flux: Flux query string. The bucket is NOT auto-substituted — include from(bucket:"<bucket>") |> range(start: -1h) |> ... yourself. bucket: name surfaced in the response for context (does not modify the query).

Reads InfluxDB URL from config (influxdb.url, default localhost:8086) and the org + token from the env vars named in influxdb.org_env / influxdb.token_env (default INFLUXDB_ORG / INFLUXDB_TOKEN).

Returns: {bucket, row_count, columns, records (list of dicts), truncated_at}. Records are capped at 500 rows to keep Claude's context manageable; if more were returned, truncated_at: 500 appears in the response.

Returns {"error": "..."} on missing token, network failure, or Flux syntax error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fluxYes
bucketNomonitoring

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Despite no annotations, the description fully discloses behavioral traits: reads config and env vars, returns specific structure, caps records at 500, error handling details. This provides complete transparency for an AI agent.

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?

The description is well-structured with clear paragraphs and front-loaded purpose. It is slightly verbose but every sentence adds value; minor redundancy could be trimmed.

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

Completeness5/5

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

Given the tool's complexity (database query), the description covers input, configuration, output schema, row limit, and error responses. It is complete and enables correct invocation.

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

Parameters5/5

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

Schema has 0% description coverage, but the description adds essential meaning for both parameters: explains flux query requirements and example, clarifies bucket is only for context. This compensates fully.

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

Purpose5/5

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

The description clearly states the verb ('Execute') and resource ('Flux query against the local InfluxDB'), and distinguishes from sibling tools like query_loki_logs by focusing on InfluxDB metrics.

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 detailed usage instructions (e.g., bucket not auto-substituted, example query format, config/env variable setup). It implicitly differentiates from siblings (InfluxDB vs Loki) but lacks explicit when-to-use or when-not-to-use statements.

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

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/bastiaan365/mcp-it-ops'

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