Delete a MongoDB user permanently from a hosting account. Use this tool when you need to remove an existing database user and confirm the action to complete the irreversible deletion.
Delete a MongoDB user. Irreversible.
| Name | Required | Description | Default |
|---|---|---|---|
| confirm | Yes | ||
| db_username | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It does add the key warning 'Irreversible,' which is valuable beyond the literal meaning of 'delete.' However, it does not explain consequences like loss of access, impact on existing sessions, or whether a confirmation flag is required.
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 extremely concise: one action sentence and one high-value warning. Every word contributes, and the core purpose is front-loaded. No redundant or filler language is present.
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?
For a destructive operation with no annotations and no output schema, the description is underspecified. It does not clarify the confirm parameter, preconditions, effects on associated databases or roles, or what happens after deletion. The irreversibility warning is important, but it is not enough to make the definition contextually complete.
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?
Schema description coverage is 0%, and the description does not explain the meaning or role of the two parameters. The parameter names and the confirm constraint provide some clues, but the description adds nothing about db_username identifying the target user or confirm being a safety confirmation.
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 a specific action on a specific resource: 'Delete a MongoDB user.' The verb and resource are unambiguous, and it distinguishes the tool from siblings like ecp_mongo_update_user_password, ecp_mongo_assign_user_to_database, and delete-user tools for other database types.
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 gives no guidance about when to use this tool versus alternatives, such as ecp_postgres_delete_user or ecp_mssql_delete_user, nor does it mention any prerequisites or exclusions. The only additional context is the warning that deletion is irreversible, which is a risk cue, not usage guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.