Skip to main content
Glama
Secure MySQL MCP Server

Secure MySQL MCP Server

by Kavi-200312

execute_approved_write

Executes a previously proposed, user-approved write operation using its short-lived approval token and requires explicit user confirmation.

Instructions

Execute a previously proposed and user-approved write operation using its short-lived approval token. Strictly requires userConfirmed: true.

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": {
      "approvalToken": "<approvalToken>",
      "userConfirmed": "<userConfirmed>"
    },
    "name": "execute_approved_write"
  }
}

Input Schema

NameRequiredDescriptionDefault
approvalTokenYesThe short-lived approval token returned by propose_write.
userConfirmedYesExplicit confirmation from the user (must be true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It discloses that the token is short-lived and that user confirmation is mandatory, and implies mutation, but it does not say whether the write is irreversible, what permissions are needed, what happens on token expiry or failure, or what the call returns. For a write-execution tool with zero annotation coverage that is a meaningful 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?

Two sentences, both front-loaded with the operative constraint and free of filler. The essential gating condition (userConfirmed: true) is stated up front rather than buried.

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 two-parameter tool with a fully documented schema and no output schema, the description covers the token source and the confirmation gate adequately. It falls short only on failure modes and irreversibility, which matter for an unannotated write tool but are secondary given the small surface.

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 both parameters are already documented in the schema, including that the token comes from propose_write and is short-lived. The description restates the userConfirmed constraint rather than adding new meaning such as token lifetime or reuse rules, 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?

The description states a specific verb and resource: it executes a previously proposed, user-approved write operation via an approval token. It distinguishes itself from the proposal step by tying itself explicitly to propose_write's token, so an agent can tell it apart from the sibling that only drafts the write.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Preconditions are clear: the operation must have been previously proposed and approved, and userConfirmed must be true. What is missing is an explicit statement of the negative case (e.g., never call before propose_write, never call without fresh user consent) and any statement about behavior on an expired or reused token.

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