Skip to main content
Glama

Generate MySQL Client

create_mysql_client
Read-onlyIdempotent

Generate a MySQL JDBC client helper class with safe connection handling for Java projects, using configurable JDBC URL, username, package, and project path.

Instructions

Generate a MySQL JDBC client helper class with safe connection handling.

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

Input Schema

NameRequiredDescriptionDefault
jdbcUrlNoDefault MySQL JDBC URL (overridable via DB_URL)
usernameNoDefault MySQL user (overridable via DB_USER)
packageNameNoPackage for the generated class
projectPathNoPath to the project directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is largely covered. The description adds only "safe connection handling" and does not resolve the key ambiguity for an agent: whether the generated class is written to disk under projectPath or returned as text, and whether an existing class would be replaced. Because the source of the generated artifact is unclear rather than explicitly contradicted, this is a gap rather than a flagged conflict.

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?

A single declarative sentence with the artifact front-loaded and no filler. It is efficient, though its brevity comes at the cost of the usage and output-location detail that would help an agent call it correctly.

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

Completeness3/5

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

The rich schema and annotations carry much of the load, and no output schema means return values needn't be described. However, for a code-generation tool taking an optional projectPath, the description omits where output lands, whether files are overwritten, and what defaults are applied when all parameters are empty.

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 description coverage is 100% and each of the four parameters (jdbcUrl, username, packageName, projectPath) is documented in the schema, including the DB_URL/DB_USER override behavior. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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?

"Generate a MySQL JDBC client helper class" names a concrete verb (generate) and a concrete artifact (JDBC client helper class), and "safe connection handling" adds a qualifier about what the generated code does. An agent can tell this apart from analysis/schema tools in the sibling list. It stops short of explicitly naming what it is not or pointing to any alternative generator.

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?

There is no when-to-use or when-not-to-use guidance: nothing states the prerequisite (an existing project at projectPath), whether it should be used before or instead of any related tool, or what happens on repeated invocation. Usage can only be inferred from the one-line purpose statement.

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