Skip to main content
Glama
jdbc-mcp-guard

jdbc-mcp-guard

by lyb-java

db_dialects

Lists supported JDBC database dialects, shows whether each driver is local, cached, or auto-downloadable, and explains how to connect databases not built in.

Instructions

列出支持的数据库方言、各自驱动是否已就绪(本地/缓存/可自动下载),以及如何接入未内置的数据库。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the three categories of information returned (dialects, driver readiness, integration path), but does not say whether the call is read-only, whether merely invoking it can trigger an auto-download, or whether any state changes — a meaningful gap given the mention of auto-downloadable drivers.

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 sentence that front-loads the primary output (dialects) and then adds the two enrichment dimensions (driver readiness, onboarding path). No filler or restatement of the tool name.

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 informational tool with no output schema, the description enumerates the returned content well enough for an agent to know it can answer both 'which dialects exist' and 'can I use this driver right now'. Only the side-effect question (downloads) is left open.

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, so there is nothing to disambiguate and the baseline is 4. The description correctly implies no input is required to enumerate dialects.

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 states a specific verb and resource: it lists the supported database dialects and reports each driver's readiness state (local / cached / auto-downloadable). That is clearly distinct from the sibling operations (connect, execute, query, inspect schema), though it never names an alternative to route agents away from.

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?

Usage is only implied: an agent would infer it should call this before attempting a connection to check driver availability or to learn how to add an unsupported backend. There is no explicit when-to-use statement, no when-not-to-use, and no mention of prerequisites or alternatives.

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