Skip to main content
Glama
Sign In
@cocaxcode/database-mcp

@cocaxcode/database-mcp

by cocaxcode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

conn_group_delete

Remove a connection group while preserving its connections, leaving them orphaned. Provide the group name to delete.

Instructions

Elimina un grupo. Las conexiones del grupo NO se eliminan pero quedaran huerfanas.

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

Input Schema

NameRequiredDescriptionDefault
nameYesNombre del grupo a eliminar

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.4

TDQS

A4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses a crucial side effect: the group's connections are not deleted but become orphaned. This is a valuable behavioral note beyond the basic action, though it doesn't cover other aspects like error conditions.

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 two sentences, front-loaded with the primary action and then the critical side effect. Every word earns its place, with no redundancy.

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 delete operation with one parameter and no output schema, the description is largely complete: it states the action and the key behavioral consequence. It could mention error handling or prerequisites, but these are not essential for a minimal viable description.

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?

The single parameter 'name' is fully described in the schema ('Nombre del grupo a eliminar'), and the description does not add additional parameter semantics. Since schema coverage is 100%, the baseline is 3; the description adds no extra parameter-level 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 clearly states it deletes a group ('Elimina un grupo'), with a specific verb and resource. It distinguishes from sibling tools like conn_delete (which deletes a connection) and conn_group_create (which creates a group).

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 usage is implied by the tool name and description, but there is no explicit guidance on when to use this over alternatives or prerequisites. It does not mention exclusions or context beyond the deletion action.

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

Deploy Server

Other Tools