Skip to main content
Glama
InfluxDB MCP Server

InfluxDB MCP Server

by Quorralyne

cloud_create_database_token

Create a new InfluxDB Cloud-Dedicated database token with per-database read or write permissions, or issue a no-access token.

Instructions

Create a new database token for InfluxDB Cloud-Dedicated cluster. Specify exact permissions per database or create a no-access token.

Permissions format: [{"database": "db_name", "action": "read|write"}, ...] Examples: • No access: omit permissions field or use [] • Read-only on 'analytics': [{"database": "analytics", "action": "read"}] • Mixed permissions: [{"database": "logs", "action": "read"}, {"database": "metrics", "action": "write"}] • Full access: [{"database": "", "action": "read"}, {"database": "", "action": "write"}]

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": {
      "description": "<description>"
    },
    "name": "cloud_create_database_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
descriptionYesDescription/name for the token
permissionsNoArray of permission objects. Each object specifies database and action. Leave empty array [] for no-access token.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the permission model, the '*' wildcard meaning, and that a no-access token is a valid outcome. It omits important behavioral facts for token creation: whether the secret is returned only once, whether the caller needs admin/operator privileges, and whether tokens expire or can be revoked later.

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 lead sentence states the action, followed by a format line and a scannable bulleted example list. The examples are numerous but each illustrates a distinct configuration, so almost nothing is wasted.

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

Completeness3/5

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

For a creation tool with no annotations and no output schema, the definition should say what is returned (e.g., the generated token value) and any privilege requirements. Those gaps leave the agent less prepared to handle the result or failures.

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?

Schema coverage is 100%, so a baseline of 3 is warranted, but the description adds real meaning with concrete permission-array examples covering mixed and full-access cases. It also surfaces that omitting the permissions field is equivalent to an empty array, which the schema does not state for the omitted case.

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?

The description states a specific verb and resource ('Create a new database token') and scopes it to 'InfluxDB Cloud-Dedicated cluster'. It does not name distinguishing siblings such as create_admin_token or create_resource_token, so the agent must infer the difference from the tool name alone.

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 through configuration examples (no-access, read-only, mixed, full access), which clarifies how to call the tool but not when to choose it over the sibling token-creation tools. No exclusions or prerequisites are stated.

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