Skip to main content
Glama
InfluxDB MCP Server

InfluxDB MCP Server

by Quorralyne

cloud_update_database_token

Update an existing InfluxDB Cloud-Dedicated database token's description or permissions, replacing its current permission set with the precise access you specify.

Instructions

Update an existing database token for InfluxDB Cloud-Dedicated cluster. Can update description and/or permissions with precise control.

Permissions format: [{"database": "db_name", "action": "read|write"}, ...] Note: Permissions completely replace existing ones - include all desired permissions. Examples: • No access: 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": {
      "token_id": "<token_id>"
    },
    "name": "cloud_update_database_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
token_idYesThe ID of the token to update
descriptionNoNew description for the token (optional)
permissionsNoArray of permission objects. Each object specifies database and action. Use empty array [] for no-access token.

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?

With no annotations, the description carries the full burden and does deliver the single most important behavior: 'Permissions completely replace existing ones - include all desired permissions', which prevents a destructive partial-update mistake. It does not state auth/permission requirements for the caller, whether the token secret is returned or rotated, or whether description alone can be updated without touching permissions.

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?

Purpose first, then the replacement warning front-loaded before the format examples, then four compact scenario bullets. Every line is actionable and none is filler.

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 3-parameter mutation tool with no annotations and no output schema, the replacement semantics and payload examples cover the highest-risk unknowns. The remaining gap is caller-side authorization and whether the response contains anything sensitive, but the core call mechanics are fully specified.

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 the baseline is 3; the description goes beyond it by giving concrete permissions payload examples (empty array, read-only, mixed, wildcard full access) that clarify the real-world shape of a nested permission list. It adds little for token_id and description, which the schema already documents fully.

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 ('Update an existing database token') and names the updatable fields (description and/or permissions). The sibling set (create/delete/get/list database tokens) is clearly separable by verb, though the description never explicitly contrasts itself with them.

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 'can update description and/or permissions', which tells the agent what the tool is for but not when to prefer it over cloud_create_database_token, cloud_delete_database_token, or regenerate_operator_token. No prerequisites or exclusions are given.

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