Skip to main content
Glama
sql-mcp
by ohankay

list_connections

Read-onlyIdempotent

Lists configured SQL Server connection profiles so you can identify available connections while keeping passwords hidden.

Instructions

List configured SQL Server connection profiles (passwords are never shown).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description still adds real value beyond that by disclosing a return-content constraint — "passwords are never shown" — which tells the agent that credentials are redacted and that secret material cannot be retrieved here. Minor gaps remain (no note on whether profiles from all configured servers are returned or what identifying fields appear).

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?

A single front-loaded sentence with zero filler; the verb and resource lead, and the credential caveat is parenthetical rather than burying the main action. Nothing is repeated from the annotations or schema.

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-parameter, read-only listing tool with rich annotations and no output schema, the description covers what matters: scope (SQL Server connection profiles) and the key security caveat about passwords. It could go slightly further by hinting at the identifying fields returned (profile name, server, database) so the agent knows what it can do with the results, but it is sufficient to call the tool correctly.

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

Parameters4/5

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

The tool takes no parameters, so per the baseline there is nothing for the description to disambiguate and a 4 is appropriate. The description does not need to compensate for any schema gaps because the schema is an empty object with full coverage.

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 uses a specific verb ("List") plus a precise resource ("configured SQL Server connection profiles"), so an agent knows exactly what it retrieves. It stops short of naming a sibling to contrast with (e.g., test_connection or add_connection), so it doesn't fully differentiate within the connection-tool family.

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?

The read-only listing framing implicitly signals when to use it (inspecting existing profiles), but there is no explicit when-to-use or when-not-to-use statement. It never mentions the natural alternatives such as test_connection for validating a profile or add_connection/remove_connection for mutating the set, so the agent must infer routing from the sibling names alone.

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