Skip to main content
Glama
cemalturkcan

MariaDB MCP Server

by cemalturkcan

suggest_query

Suggest SQL queries that should be executed manually, providing the query and reason to guide database operations with explicit user approval.

Instructions

Suggests a query that should be executed manually.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
connectionYes
queryYes
reasonNo

Implementation Reference

  • The handler for the suggest_query tool. It extracts connection, query, and reason from args, then returns a message indicating manual execution is required, along with the query details.
    case "suggest_query": {
      const { connection, query, reason } = args || {};
      return ok({
        message: "MANUAL EXECUTION REQUIRED",
        connection,
        reason: reason || "Write operation",
        query,
      });
    }
  • src/tools.js:98-110 (registration)
    The tool definition registration for suggest_query. Defines name, description, and inputSchema with connection (string), query (string), and reason (string). connection and query are required.
    tools.push({
      name: "suggest_query",
      description: "Suggests a query that should be executed manually.",
      inputSchema: {
        type: "object",
        properties: {
          connection: { type: "string" },
          query: { type: "string" },
          reason: { type: "string" },
        },
        required: ["connection", "query"],
      },
    });
Behavior2/5

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

No annotations are provided, so the description must cover behavioral traits. It only states the tool suggests a query for manual execution, leaving out details like side effects, permissions, or what happens when invoked. This is minimal disclosure for a tool with no annotations.

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

Conciseness2/5

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

The description is a single sentence that is concise but under-specifies the tool. It does not earn its place due to lack of substance; it is too sparse to be helpful beyond stating the basic action.

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?

Given the tool has three parameters and no output schema, the description should provide more context. It fails to explain the role of each parameter, the outcome of the suggestion, or any prerequisites. The description is incomplete for effective tool selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage, and the tool description adds no meaning to the parameters (connection, query, reason). With no compensation from the description, the agent has no insight into parameter semantics beyond their names.

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 suggests a query for manual execution, distinguishing it from sibling tools like execute_select. The verb 'suggests' and resource 'query' are specific, and the manual execution note differentiates its purpose.

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?

The description implies the tool is for suggesting queries rather than executing them, especially given the sibling execute_select. However, there is no explicit guidance on when to use it or when not to, nor any mention of alternatives beyond the implied distinction.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cemalturkcan/mariadb-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server