DBJavaGenix

db_query_execute

Execute custom SQL SELECT queries on a connected database with configurable row limits.

Instructions

Execute custom SQL query (SELECT only for safety)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "connection_id": "<connection_id>",
      "query": "<query>"
    },
    "name": "db_query_execute"
  }
}

Input Schema

Name	Required	Description
`connection_id`	Yes	Connection identifier from db_connect_test
`query`	Yes	SQL SELECT query to execute
`limit`	No	Maximum number of rows to return

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1May 26, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. It states 'SELECT only for safety', implying read-only behavior, but lacks detail on error handling, performance impact, or authentication requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence effectively communicates core function. Could potentially include more details without becoming verbose, but current version is concise and direct.

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?

No output schema exists, yet description does not explain what is returned (e.g., rows, columns, format). For a tool executing arbitrary queries, more context is needed for safe and effective use.

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 parameters are already well-documented. Description adds no extra semantic meaning beyond the schema descriptions.

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?

Clearly states the action (Execute), resource (custom SQL query), and constraint (SELECT only). Distinguishes from sibling tools like db_connect_test and db_query_tables.

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?

Implicitly restricts usage to SELECT queries via '(SELECT only for safety)', but does not explicitly state when to use this tool versus alternatives like db_query_tables or db_table_columns.

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