Skip to main content
Glama
yaoxiaolinglong

MCP-MongoDB-MySQL-Server

execute

Execute INSERT, UPDATE, or DELETE queries to modify data in MySQL or MongoDB databases through a standardized interface.

Instructions

Execute an INSERT, UPDATE, or DELETE query

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sqlYesSQL query (INSERT, UPDATE, DELETE)
paramsNoQuery parameters (optional)

Implementation Reference

  • The handler function that executes INSERT, UPDATE, or DELETE SQL queries on a MySQL database connection. Ensures connection, validates non-SELECT query, executes with optional parameters, and returns JSON result.
    private async handleExecute(args: any) {
      await this.ensureConnection();
    
      if (!args.sql) {
        throw new McpError(ErrorCode.InvalidParams, 'SQL query is required');
      }
    
      const sql = args.sql.trim().toUpperCase();
      if (sql.startsWith('SELECT')) {
        throw new McpError(
          ErrorCode.InvalidParams,
          'Use query tool for SELECT statements'
        );
      }
    
      try {
        const [result] = await this.connection!.query(args.sql, args.params || []);
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(result, null, 2),
            },
          ],
        };
      } catch (error) {
        throw new McpError(
          ErrorCode.InternalError,
          `Query execution failed: ${getErrorMessage(error)}`
        );
      }
    }
  • The input schema for the 'execute' tool, defining required 'sql' string for non-SELECT queries and optional 'params' array.
    {
      name: 'execute',
      description: 'Execute an INSERT, UPDATE, or DELETE query',
      inputSchema: {
        type: 'object',
        properties: {
          sql: {
            type: 'string',
            description: 'SQL query (INSERT, UPDATE, DELETE)',
          },
          params: {
            type: 'array',
            items: {
              type: ['string', 'number', 'boolean', 'null'],
            },
            description: 'Query parameters (optional)',
          },
        },
        required: ['sql'],
      },
    },
  • src/index.ts:541-542 (registration)
    Registration in the CallToolRequestHandler switch statement that routes 'execute' tool calls to the handleExecute method.
    case 'execute':
      return await this.handleExecute(request.params.arguments);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool executes data manipulation queries (INSERT, UPDATE, DELETE), implying mutation operations, but doesn't cover critical aspects like permissions required, transaction handling, error behavior, or output format. For a mutation tool with zero annotation coverage, this is a significant gap.

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?

The description is extremely concise—a single sentence with zero waste. It's front-loaded with the core purpose and uses clear, direct language. Every word earns its place, making it easy for an agent to parse quickly.

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's complexity (executing mutable SQL queries), lack of annotations, and no output schema, the description is incomplete. It doesn't address safety concerns, error handling, or what the tool returns (e.g., row counts, success/failure). For a mutation tool in a database context, this leaves critical gaps for an agent.

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%, so the schema already documents both parameters ('sql' and 'params') adequately. The description adds no additional parameter semantics beyond what's in the schema (e.g., no examples of SQL syntax or param usage). Baseline 3 is appropriate when the schema does the heavy lifting.

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 clearly states the tool's purpose: 'Execute an INSERT, UPDATE, or DELETE query.' It specifies the verb ('execute') and the resource/action type (SQL queries for data manipulation). However, it doesn't explicitly differentiate from sibling tools like 'query' (which likely handles SELECT queries) or 'add_column'/'create_table' (DDL operations), so it's not a perfect 5.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'query' for SELECT operations or DDL tools for schema changes, nor does it specify prerequisites (e.g., database connection). This leaves the agent with minimal context for tool selection.

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/yaoxiaolinglong/mcp-mongodb-mysql-server'

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