Skip to main content
Glama
dsh-databases

dsh-databases

by nvznc

Listar bases de datos

list_databases
Read-onlyIdempotent

Discover accessible MSSQL, MySQL, and PostgreSQL databases with status and size when available, so you can identify which databases exist before querying tables.

Instructions

Lista las bases de datos a las que tiene acceso la conexión elegida (mssql, mysql o postgres), con estado y tamaño cuando el motor lo expone. Úsala para descubrir qué bases existen antes de consultar tablas.

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

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.
includeSystemNoIncluye las bases de sistema del motor (por defecto false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety is covered. The description adds value beyond that by disclosing that results are limited to what the connection can access and that status and size are returned only when the engine exposes them, which warns of a variable result shape. Without an output schema this partial disclosure of return content is genuinely useful.

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 sentences with no filler: purpose and scope first, then the workflow use case. Every clause earns its place and nothing is front-loaded incorrectly.

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 zero-required-parameter discovery tool with no output schema, the definition covers what is listed and under which engine conditions. The only minor gap is not clarifying whether the returned fields differ per engine or how failures on an unreachable connection surface, but the essentials are present.

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%, with each of the four parameters documented including defaults and the engine enum, so the schema carries the parameter burden. The description only restates the engine values and the connection scoping, adding no syntax or edge-case meaning (e.g. how includeSystem interacts with size/status reporting). 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?

Names a specific verb and resource ("Lista las bases de datos") and scopes it to the chosen connection and the three supported engines. The final clause, "antes de consultar tablas", implicitly separates it from list_tables, but it never names that sibling explicitly, so the differentiation is contextual rather than stated.

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 use case: discover which databases exist before querying tables, which places it correctly in the workflow ahead of list_tables/describe_table. It stops short of explicit exclusions or a direct pointer to an alternative (e.g. when to use list_tables instead).

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