Skip to main content
Glama
multidb-mcp

multidb-mcp

test_connection

Verifies a configured database connection, returning server version and current schema to confirm connectivity before running queries.

Instructions

Verify the database connection and return server version and current schema. Use to check connectivity before running queries.

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

Input Schema

NameRequiredDescriptionDefault
connectionNoName of the configured connection to test. Omit when only one is configured.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It usefully discloses that the call surfaces server version and current schema, implying a non-destructive diagnostic read, but says nothing about failure behavior, timeouts, or what happens when the named connection is invalid or missing.

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 short sentences, zero waste: the action and its return payload come first, followed by the usage cue. Nothing is buried or redundant.

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 simple one-optional-parameter diagnostic with no output schema, the description covers purpose, return contents, and calling context — enough to invoke it correctly. The only missing piece is error/comportment information, which matters somewhat given the complete absence of annotations.

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?

There is a single optional parameter already fully documented in the schema, including the rule to omit it when only one connection exists. The description adds no further meaning beyond that, so the high schema coverage sets the baseline at 3.

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 ("Verify the database connection") and even the payload (server version and current schema), which is more than a restatement of the name. It does not explicitly contrast itself with siblings such as list_connections or execute_sql, so differentiation is inferred rather than stated.

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?

Gives a clear triggering context: use it to check connectivity before running queries, which implicitly positions it ahead of execute_sql. It stops short of naming alternatives or stating when not to use it (e.g., after a connection is already known good).

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