Remove a database connection from BetterDB by specifying its instance ID to clean up unused resources.
Remove a connection from BetterDB.
| Name | Required | Description | Default |
|---|---|---|---|
| instanceId | Yes | The instance ID to remove |
Changes observed during successful MCP inspections.
v0.33.0v0.31.0v0.20.2v0.20.1v0.16.0Input schema / additionalPropertiesRemoved value: -falsev1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations; description provides no details on side effects, irreversibility, or any behavioral traits beyond the action itself.
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?
Extremely short but lacks substantive content; it is under-specified rather than concise.
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?
No output schema, no description of return values, prerequisites, or consequences. Incomplete for a deletion tool.
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 100%; the single parameter instanceId is documented in the schema. Description adds no extra meaning beyond the schema.
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 action (remove), resource (connection), and scope (from BetterDB). It distinguishes from siblings like add_connection and test_connection.
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?
No guidance on when to use this tool vs alternatives, no prerequisites, no conditions for correct usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.