Skip to main content
Glama
InfluxDB MCP Server

InfluxDB MCP Server

by Quorralyne

cloud_delete_database_token

Deletes a database token from an InfluxDB Cloud-Dedicated cluster by token ID, enabling token cleanup and access revocation. This action is irreversible.

Instructions

Delete a database token from InfluxDB Cloud-Dedicated cluster. This action cannot be undone.

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_delete_database_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
token_idYesThe ID of the token to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/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 usefully discloses irreversibility ('This action cannot be undone'), which is real behavioral context. However, it omits required permissions/scope, whether the token is revoked immediately, and what happens to requests already using that token.

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?

Two short sentences, action first and the permanence warning second, with no filler. Slight redundancy in restating the product family, but nothing that wastes an agent's attention.

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 one-parameter destructive tool with no annotations and no output schema, the irreversibility warning covers the most important gap, but the definition leaves out permission requirements and post-deletion behavior. Adequate, not complete.

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 coverage is 100% with a single, well-described token_id parameter, so the schema does the heavy lifting. The description adds no format, source, or retrieval guidance (e.g., obtain via cloud_list_database_tokens) beyond what the schema already states.

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?

Specific verb (Delete) plus resource (database token) scoped to 'InfluxDB Cloud-Dedicated cluster', which lets an agent distinguish it from deployment-agnostic siblings like delete_token. It stops short of naming which sibling to prefer, but the action 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?

No explicit when-to-use or when-not-to-use guidance and no mention of alternatives such as delete_token, even though the catalog contains similarly named deletion tools. The only routing signal is the implicit 'Cloud-Dedicated cluster' scope.

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