MSSQL MCP Reader

list_databases

List databases on a SQL Server instance, filtered by environment, state, and system database inclusion. Requires server-level access and respects environment policies.

Instructions

Lists databases on the SQL Server instance. Requires server-level access. Filtered by environment policies.

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

Name	Required	Description
`environment`	No	Target environment name (optional, uses default if not specified)
`includeSystemDbs`	No	Include system databases (master, msdb, model, tempdb). Default: false
`stateFilter`	No	Filter by database state. Default: ONLINE

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.2May 29, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. It discloses access requirements and environment filtering, but does not state if the operation is read-only or describe any side effects. Adequate but not fully transparent.

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?

The description is two sentences, front-loaded with the action, and contains no unnecessary words. Every sentence provides value.

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?

Given no output schema, the description explains the tool's purpose and constraints (access, filtering). It does not specify the return format, but for a listing tool, this is often implied. It is complete enough for most scenarios.

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?

All three parameters have descriptions in the schema (100% coverage). The description adds no further meaning beyond the schema, so the baseline score of 3 is appropriate.

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 clearly states 'Lists databases on the SQL Server instance' with a specific verb and resource. It distinguishes from sibling tools like 'list_tables' and 'describe_table' by focusing on databases.

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?

The description provides context on when to use the tool by specifying 'Requires server-level access' and 'Filtered by environment policies'. It does not explicitly mention alternatives or when not to use, but the constraints are clear.

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

Deploy Server