Skip to main content
Glama
multidb-mcp

multidb-mcp

list_connections

List all configured database connections with their type, host, and schema so you can choose the right connection name before querying. Passwords are never exposed.

Instructions

List all configured database connections with their type, host and schema. Never exposes passwords. Call this first when unsure which connection name to use.

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 observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the return shape fields and the security guarantee 'Never exposes passwords', but says nothing about permissions required, whether results are paginated/cached, or how unreachable connections are reported.

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?

Three short sentences with zero filler: purpose and return fields first, security guarantee second, usage trigger last. Every sentence carries distinct information.

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 trivial zero-parameter read tool with no annotations and no output schema, the definition covers what it does, what it returns, a safety property, and a usage trigger. Only operational details such as auth requirements or error behavior are absent.

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 zero parameters, which is the baseline case where no parameter semantic guidance is needed. The description correctly implies a no-argument enumeration rather than suggesting any filtering options that might mislead.

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?

States a specific verb and resource ('List all configured database connections') plus the fields returned (type, host, schema), so an agent immediately knows this enumerates connection configs rather than table data. It never explicitly contrasts itself with siblings like list_tables or describe_table, leaving the differentiation to inference from the word 'connections'.

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?

'Call this first when unsure which connection name to use' gives a clear situational trigger and even prescribes ordering relative to other tools. It stops short of naming a concrete alternative (e.g. test_connection) or stating when not to call it.

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