every-db-mcp

db_test_connection

Check if a database is accessible by testing connectivity to MySQL, GaussDB, Oracle, or DM8. Ensure your database is reachable before executing queries.

Instructions

Test connectivity to a specific database

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

Input Schema

Name	Required	Description	Default
`database`	No	Database ID to test (default: mysql-dev). Available: mysql-dev, gaussdb-dev, oracle-dev, dm8-dev

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 27, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations exist, so the description must fully disclose behavior. It states 'test connectivity' which implies no side effects, but does not clarify failure modes, return format, or whether any state is modified. Minimal disclosure.

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?

Extremely concise (6 words), no unnecessary information. Every word serves a purpose for a tool with a single optional parameter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Although the tool is simple, the description omits what the tool returns (e.g., success/failure status, error messages). Given no output schema, this is a critical gap for an agent to interpret results.

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?

Schema coverage is 100%, so the baseline is 3. The description does not add any additional meaning beyond what the schema already provides for the 'database' parameter.

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 the tool's action ('Test connectivity') and resource ('database'), distinguishing it from sibling tools like db_query or db_execute. It is specific and unambiguous.

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?

No guidance on when to use this tool vs alternatives such as db_query. Siblings are listed but no contextual differentiation or prerequisites are provided.

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

Deploy Server