Skip to main content
Glama
dsh-databases

dsh-databases

by nvznc

Listar tablas y vistas

list_tables
Read-onlyIdempotent

Explore an unfamiliar database schema by listing tables and views filtered by schema or name, returning type, approximate row counts, and dates when the engine exposes them.

Instructions

Lista tablas y/o vistas de la base elegida, filtradas por esquema o por texto en el nombre. Devuelve esquema, nombre, tipo, filas aproximadas y fechas cuando el motor las expone. Es el primer paso para explorar un esquema desconocido en cualquier motor.

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

Input Schema

NameRequiredDescriptionDefault
kindNoTipo de objeto (por defecto all).
engineNoMotor de base de datos. Por defecto usa MSSQL_ENGINE del .env (mssql si no existe).
schemaNoEsquema (mssql/postgres), por ejemplo "dbo" o "public".
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.
nameContainsNoFragmento del nombre de la tabla.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint, so safety is covered. The description adds real value by disclosing the returned fields (schema, name, type, approximate row counts, dates) and the important caveat that dates are only present when the engine exposes them, which is essential given there is no output schema.

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, front-loaded with the action, then the return shape, then the usage cue. No filler and no repetition of the name or title.

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 six-parameter, all-optional read tool with full schema coverage, the definition covers purpose, filters, return fields, and engine-agnostic behavior. It stops short of mentioning result-size limits or pagination, which is the only notable gap.

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%, so the schema already documents all six parameters including defaults and enums. The description only restates the two filtering axes (schema and name text), so the baseline of 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?

The description gives a specific verb and resource (list tables and/or views) plus the two filter modes (schema, name substring). It does not explicitly differentiate itself from siblings like list_databases or describe_table, so an agent must infer that databases must be chosen first from the description itself.

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?

"Es el primer paso para explorar un esquema desconocido en cualquier motor" gives a genuine when-to-use cue. However, there is no when-not guidance and no named alternative (e.g., describe_table for column detail), leaving the routing to inference.

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