Skip to main content
Glama
InfluxDB MCP Server

InfluxDB MCP Server

by Quorralyne

cloud_list_database_tokens

List all InfluxDB Cloud-Dedicated database tokens and retrieve their permissions and creation dates to audit access and manage token inventory.

Instructions

List all database tokens for InfluxDB Cloud-Dedicated cluster. Returns token information including permissions and creation dates.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cloud_list_database_tokens"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/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 return contents ('permissions and creation dates'), which is genuinely useful behavior beyond the schema, but it says nothing about whether secret token values are exposed, what permissions or auth are required to list tokens, or whether results are paginated — material gaps for a credential-listing tool.

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 with no redundant wording; the purpose is front-loaded and the return-content note follows immediately. Every clause earns its place.

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 simple zero-parameter list operation with no output schema, the description covers what the tool does and roughly what comes back, which is close to sufficient. The remaining gaps are around sensitive-value exposure and pagination, minor for a tool of this complexity.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly implies the cluster context is fixed rather than passed as input.

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 ('List all database tokens') scoped to an 'InfluxDB Cloud-Dedicated cluster', which an agent can distinguish from the sibling token types by name. It does not explicitly contrast with list_admin_tokens or list_resource_tokens, so the differentiation is implied by the 'database' qualifier rather than spelled out.

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 implied by the resource name — an agent would infer this is the tool for enumerating database-scoped tokens. However, there is no explicit when-to-use guidance, no mention of prerequisites such as cluster or account identifiers, and no pointer to the sibling list tools for other token scopes.

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