Skip to main content
Glama
InfluxDB MCP Server

InfluxDB MCP Server

by Quorralyne

get_measurements

Lists all measurements (tables) in a specified InfluxDB database, using information_schema to discover available tables for schema inspection and query planning.

Instructions

Get a list of all measurements (tables) in a database (all versions). Uses the InfluxDB information_schema.columns to discover tables.

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": {
      "database": "<database>"
    },
    "name": "get_measurements"
  }
}

Input Schema

NameRequiredDescriptionDefault
databaseYesName of the database to list measurements from

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses the implementation detail that discovery goes through information_schema.columns and that it works across all versions, but says nothing about permissions, behavior for a nonexistent or empty database, or the shape of the returned list.

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?

Two short sentences, front-loaded with what is returned and followed by the mechanism. No padding or redundant restatement of the tool name.

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?

For a one-parameter read tool with no output schema and no annotations, the definition covers the essentials: what it returns, from where, and how it discovers the data. Error and empty-result behavior would round it out but are minor gaps.

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?

There is a single required parameter with 100% schema description coverage, so the schema already defines the database argument fully. The description adds no format hints (e.g., case sensitivity or whether the database must exist) beyond what the schema provides.

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 ('get a list of all measurements') and disambiguates the InfluxDB term by equating measurements with tables, which helps agents unfamiliar with the vocabulary. It stops short of distinguishing itself from the sibling get_measurement_schema, so an agent must infer that this returns names only.

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?

Usage is only implied by the purpose: list table names, presumably before querying or fetching a schema. There is no explicit statement of when to prefer get_measurement_schema or execute_query over this tool, and no preconditions are named.

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