Skip to main content
Glama
dsh-databases

dsh-databases

by nvznc

Información del servidor

server_info
Read-onlyIdempotent

Get version, host, current user, and start time of a connection's server to verify the database engine and host the MCP is connected to.

Instructions

Muestra versión, host, usuario actual y fecha de arranque del servidor de la conexión elegida. Sirve para confirmar a qué servidor y motor se está conectando el MCP.

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

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.8/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 the safety profile is covered. The description adds real value beyond them by specifying the exact payload (version, host, current user, startup timestamp) and that the result is scoped to the selected connection — important since no output schema exists. It stops short of noting any permission or auth requirements.

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, zero filler: the first front-loads what is returned, the second states the purpose. Nothing is repeated from the schema or annotations and no sentence is expendable.

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 three-parameter, all-optional read tool with fully documented schema and clear annotations, the description covers what the agent needs: the return fields and the scoping intent. The absence of an output schema is compensated by the enumerated fields; only the relationship to the connectivity-check siblings remains unaddressed.

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 all three optional parameters (engine, database, connection) documented in the schema including defaults and env-var fallbacks. The description only alludes to the connection scope via "la conexión elegida" and adds no default-resolution or precedence detail, so the 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?

The description opens with a specific verb-plus-resource ("Muestra versión, host, usuario actual y fecha de arranque del servidor") and enumerates exactly what is returned, so an agent knows this is a metadata/inspection tool. It implicitly separates itself from connectivity siblings by framing the goal as confirming which server and engine the MCP is bound to, though it never names those siblings.

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?

"Sirve para confirmar a qué servidor y motor se está conectando el MCP" gives a clear implied use case, so the agent knows when this tool is relevant. However, there is no explicit guidance on when to prefer it over test_connection (connectivity check) or list_connections (enumerate configured connections), and no exclusion conditions are stated.

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