Skip to main content
Glama
InfluxDB MCP Server

InfluxDB MCP Server

by Quorralyne

cloud_get_database_token

Retrieve a specific InfluxDB Cloud-Dedicated database token by ID to inspect its details.

Instructions

Get details of a specific database token by ID for InfluxDB Cloud-Dedicated cluster.

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

Input Schema

NameRequiredDescriptionDefault
token_idYesThe ID of the token to retrieve

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/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. 'Get details' implies a read, but it does not state whether the token's secret value is returned, whether special permissions are required, or what happens on an invalid/not-found ID — all material concerns for a credential-related resource.

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?

One clean, front-loaded sentence with no filler or repetition. It is efficient, though slightly thin for a credential-fetching operation.

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?

The tool is simple (one param, no nesting, no output schema), and the parameter is fully documented. However, with no annotations and no output schema, the description should say at least roughly what is returned — especially whether the token secret is included — which it omits.

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?

There is a single required parameter with 100% schema description coverage, so the schema already explains token_id. The description adds only that the lookup is by ID, which is consistent but not additive; baseline 3 applies.

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 ('Get details of a specific database token by ID') plus the product context (InfluxDB Cloud-Dedicated). The 'by ID' phrasing implicitly separates it from the list-style sibling, but no sibling is named explicitly.

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 only implied: you fetch a single token when you already know its token_id. There is no explicit when-to-use vs. cloud_list_database_tokens guidance, no statement about what to do if you don't have an ID, and no mention of related siblings like cloud_update_database_token.

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