@cocaxcode/database-mcp

Overview Schema Source Related Servers Discussions Admin

conn_delete

Delete a database connection after explicit user confirmation. Use this to remove an existing connection by name, with confirm set to true only after user approval.

Instructions

Elimina una conexion. IMPORTANTE: pide confirmacion al usuario antes de llamar esta tool con confirm=true.

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": {
      "name": "<name>"
    },
    "name": "conn_delete"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Nombre de la conexion a eliminar
`confirm`	No	Debe ser true para confirmar. Pregunta al usuario antes de poner true.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.4Aug 21, 2026

TDQS

A4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full behavioral burden. It discloses the destructive nature ('Elimina') and, more importantly, mandates user confirmation before setting confirm=true. It does not mention permanence or cascading effects, but the key safety behavior is clearly stated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise: one short declarative sentence plus a focused safety warning. Every word earns its place and the critical instruction is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple 2-parameter deletion tool with no output schema and no annotations, the description plus schema cover purpose, parameters, and the essential confirmation gate. It lacks some side-effect detail but is otherwise complete enough for safe invocation.

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 description coverage is 100%, so the schema fully explains both 'name' and 'confirm'. The description mostly reinforces the confirm requirement already present in the schema without adding substantial new parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Elimina una conexion' clearly states the tool's verb and resource: deleting a connection. This is unambiguous and distinguishes it from sibling tools like conn_create, conn_set, or conn_rename.

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?

The 'IMPORTANTE: pide confirmacion al usuario antes de llamar esta tool con confirm=true' provides a critical precondition for safe invocation. However, it does not explicitly discuss when to prefer this tool over alternatives or mention any exclusions.

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