Skip to main content
Glama
InfluxDB MCP Server

InfluxDB MCP Server

by Quorralyne

get_measurement_schema

Retrieve column names, types, and time/tag/field categories for a selected measurement and database to inspect its schema before querying or writing data.

Instructions

Get the schema (column information) for a specific measurement/table (all versions). Shows column names, types, and categories (time/tag/field).

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>",
      "measurement": "<measurement>"
    },
    "name": "get_measurement_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
databaseYesName of the database containing the measurement
measurementYesName of the measurement to describe

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/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 burden. It does disclose the returned content and the notable scope detail that all versions of the measurement are covered, but it says nothing about permissions, behavior when the measurement does not exist, or whether results are paginated.

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 compact sentences with zero filler: the action and scope come first, and the return contents follow immediately. Every clause ('all versions', 'time/tag/field') carries 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?

With no output schema, the description usefully compensates by enumerating what the response contains (names, types, categories). Only edge-case behavior, such as unknown measurement or permission failure, is left unaddressed for this simple two-parameter read 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 parameters are already documented. The description adds only a small amount of meaning by equating 'measurement' with 'table' and implying the database scopes the lookup; baseline 3 applies when the schema does the heavy lifting.

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 the schema ... for a specific measurement/table') and goes further by naming what is returned: column names, types, and time/tag/field categories. It does not explicitly contrast itself with siblings such as get_measurements, but the purpose is unambiguous.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no prerequisites, and no named alternative (e.g., get_measurements for listing tables vs. this tool for inspecting one). An agent must infer that this is a discovery step before writing a query.

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