Skip to main content
Glama
sql-mcp
by ohankay

list_databases

Read-onlyIdempotent

Retrieve SQL Server databases with state, recovery model, compatibility level, and size in MB to inspect inventory and assess configuration.

Instructions

List databases with state, recovery model, compatibility level and size (MB).

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
connectionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuine value by enumerating the returned attributes, which is not in any structured field. However it says nothing about what happens when connection is omitted (does it default to a current connection?) or whether results are ordered or paginated.

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?

One short sentence, front-loaded with the action and immediately followed by the payload. Nothing is wasted, though brevity here is partly under-specification rather than discipline.

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?

With no output schema, listing the returned columns is exactly the right compensation, and annotations cover safety. The gap is the undocumented connection argument and no explanation of default scope, which matters for a tool whose whole job is enumerating a target server's databases.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single `connection` parameter, so the description is the only place meaning could be supplied — and it ignores the parameter entirely. An agent cannot tell from either source whether null means the default connection or all connections.

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 databases') and enumerates the columns returned (state, recovery model, compatibility level, size in MB), so an agent knows exactly what comes back. It does not distinguish itself from siblings such as list_connections or list_objects, but the resource noun is distinctive enough to separate them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool versus alternatives, no prerequisites, and no note that the optional connection argument selects which server to inspect. Usage must be inferred entirely from the name.

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