Skip to main content
Glama
dsh-databases

dsh-databases

by nvznc

Eliminar conexión guardada

remove_connection
DestructiveIdempotent

Delete a saved named database connection at runtime without changing .env or config file entries.

Instructions

Elimina una conexión creada con save_connection. No afecta a las del .env ni a configs/connections.json.

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": "remove_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesNombre de la conexión guardada.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so safety and repeat-call behavior are covered. The description adds the valuable scope detail of what exactly is destroyed (only entries persisted via save_connection) versus what is left untouched, though it says nothing about file storage or what happens when the name is absent.

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?

Two short sentences, the destructive scope front-loaded and the exclusion second, with no filler. Every clause carries actionable information for the caller.

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 one-parameter delete tool with rich annotations and no output schema, the description covers purpose and scope adequately. The only remaining gap is failure behavior for unknown names, which the idempotentHint largely implies.

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 has 100% schema description coverage, so the baseline is 3. The description only implies that the name must match the identifier used at save time; it adds no syntax, formatting, or matching rules beyond the schema.

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 names a specific verb and resource ("Elimina una conexión") and immediately narrows the scope to connections created by save_connection, which is the sibling an agent would confuse this with. The exclusion of .env and configs/connections.json further disambiguates it from other connection sources.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-not guidance: connections from .env or configs/connections.json are not affected, so the agent knows not to call this for those. It does not name an alternative action for the excluded cases (e.g., editing the env file or config directly), leaving that to inference.

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