Delete an InfluxDB database by supplying its exact name from the database list. Use this to remove a database you no longer need.
Delete a database from InfluxDB. Use the exact database name as returned by the list_databases tool.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Name of the database to delete (use exact name from database list) |
Changes observed during successful MCP inspections.
v1.4.1-test.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description must fully disclose behavioral traits. It states the action but does not explicitly mention that the deletion is permanent, cannot be undone, or that it removes all data in the database. It also does not address permission requirements or error conditions, which is a significant gap for a destructive operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two concise sentences with no redundant information. It front-loads the core function and adds a practical usage tip, making it efficient and easy to parse.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple with one parameter and no output schema. The description covers the main action and parameter sourcing, but omits details about the permanence of deletion and potential error scenarios. Given the simplicity, the description is adequate but could be enhanced with a note on irreversible consequences.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema fully documents the single 'name' parameter with a description. The description adds value by instructing the agent to use the exact database name returned by list_databases, providing a reliable source for the parameter value. This goes beyond the schema's basic field description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function with a specific verb and resource ('Delete a database from InfluxDB'), distinguishing it from sibling tools like create_database, update_database, and list_databases. The added guidance about using the exact name from list_databases reinforces the purpose.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context for when to use this tool (when a database needs to be deleted) and offers a specific prerequisite (use the exact database name from list_databases). It does not explicitly mention when not to use it or enumerate alternatives, but no direct alternatives are apparent among the sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.