Skip to main content
Glama
dsh-databases

dsh-databases

by nvznc

Listar conexiones y motores

list_connections
Read-onlyIdempotent

Lists supported database engines and configured named connections from .env, configs/connections.json, and saved connections so users can choose the right connection for other database tools.

Instructions

Muestra los motores soportados (mssql, mysql, postgres) y las conexiones configuradas: la del .env ("default"), las declaradas en configs/connections.json y las guardadas con save_connection. Usa los nombres que devuelve en el parámetro "connection" del resto de herramientas.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_connections"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), so the description's added value is showing that results merge three distinct storage locations, including a file-based config and the .env default. That side-effect-free aggregation detail is real behavioral context beyond the annotations; only the listing format and what happens if a config file is absent are unstated.

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

Conciseness4/5

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

A single front-loaded sentence plus one practical closing instruction; every clause carries information. It is dense rather than padded, though the Spanish text is long enough to be one clause away from being run-on.

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?

There is no output schema, so the description takes on the job of saying what comes back: the supported engine list and the configured connections by origin. That plus the 'use these names elsewhere' instruction covers what an agent needs before calling it; only edge cases like an empty or missing connections file go unmentioned.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so there is nothing for the description to disambiguate at the input level. Baseline for a 0-parameter schema applies.

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 gives a specific verb and resource ('Muestra los motores... y las conexiones configuradas') and then enumerates the exact three sources it aggregates: .env ('default'), configs/connections.json, and save_connection. An agent can tell immediately that this is a discovery/enumeration tool rather than a connector or query tool.

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 downstream guidance: use the returned names in the 'connection' parameter of the other tools, which is a concrete workflow instruction tying this tool to its siblings. It does not state when not to use it, but for a zero-parameter discovery tool there is little plausible misuse to exclude.

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