List all measurements (tables) in an InfluxDB database or bucket by querying information_schema.columns, helping you discover available data for queries.
Get a list of all measurements (tables) in a database/bucket (all versions). Uses the InfluxDB information_schema.columns to discover tables.
| Name | Required | Description | Default |
|---|---|---|---|
| database | Yes | Name of the database/bucket to list measurements from |
Changes observed during successful MCP inspections.
v1.4.1-test.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It discloses that the tool uses InfluxDB's information_schema.columns, implying a read-only metadata query. However, it does not clarify permissions, response format, or the exact meaning of 'all versions', leaving behavioral gaps.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences with no wasted words. It front-loads the core action and includes a useful technical detail about how discovery works, making it efficient and well-structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter list tool, the description covers the main purpose and mechanism. Minor ambiguity around 'all versions' and lack of return structure keep it from being fully complete, but it is sufficient for most invocation scenarios.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema fully describes the 'database' parameter with 100% coverage. The description only repeats 'database/bucket' and adds no extra constraints or format details, warranting the baseline score of 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns a list of all measurements (tables) in a database/bucket, using a specific verb and resource. It also distinguishes itself from sibling tools like list_tables by specifying InfluxDB context and 'all versions', making the purpose unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use the tool: when you need to discover measurements in an InfluxDB database/bucket. However, it does not explicitly mention alternatives or when not to use it, leaving some room for misinterpretation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.