Skip to main content
Glama
dsh-databases

dsh-databases

by nvznc

Probar conexión

test_connection
Read-onlyIdempotent

Validates a database connection and returns real server details (version, host, user) or the exact error, useful after editing configs or saving a connection.

Instructions

Abre una conexión y devuelve la información real del servidor (versión, host, usuario) o el error exacto. Úsala después de editar configs/connections.json o de guardar una conexión.

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

Input Schema

NameRequiredDescriptionDefault
engineNoMotor de base de datos. Por defecto usa MSSQL_ENGINE del .env (mssql si no existe).
databaseNoNombre de la base de datos. Si se omite se usa la de la conexión (por defecto master).
connectionNoNombre de la conexión definida en configs/connections.json, guardada con save_connection o "default" (.env). Si se omite se usa la conexión por defecto o la indicada por DSH_MCP_SQL_CONNECTION.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world behavior, so the safety profile is covered. The description adds that it actually opens a network connection and returns either real server metadata or the exact error, which is useful beyond the annotations. It does not mention timeout behavior, whether failures surface as the returned value rather than an exception, or auth/prerequisite requirements.

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?

Two compact sentences, front-loaded with the outcome and followed by the usage trigger. No wasted wording; slightly terse given the tool's diagnostic role.

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

Completeness3/5

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

For a three-optional-parameter diagnostic tool with no output schema, the description covers purpose, trigger and the shape of the return (version/host/user or error). Gaps remain around failure semantics, expected latency, and whether a connection is left open or closed.

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 coverage is 100%, and each parameter already documents its default fallback (MSSQL_ENGINE, master, default connection / DSH_MCP_SQL_CONNECTION). The description adds no parameter-specific meaning beyond the schema, so baseline 3 applies.

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

Purpose4/5

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

States a specific verb and outcome: opens a connection and returns real server information (version, host, user) or the exact error. That distinguishes it from siblings like list_connections (which presumably only reads config) and server_info. It doesn't explicitly name a sibling, so it falls short of a 5.

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?

Gives a clear triggering condition: use it after editing configs/connections.json or after saving a connection. That is concrete and actionable, but there is no explicit exclusion of alternatives (e.g. when to prefer server_info or list_connections instead of probing).

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