Skip to main content
Glama
sussa3007

MySql MCP Server

set_readonly

Control database access by enabling or disabling read-only mode for MySQL databases to restrict write operations or allow updates as needed.

Instructions

Enable or disable read-only mode

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
readonlyYesSet to true to enable read-only mode, false to disable

Implementation Reference

  • Handler function for the 'set_readonly' tool. Sets the 'readonly' flag in the global connectionConfig based on the input boolean parameter and returns a confirmation message.
    case "set_readonly": {
      try {
        const readonly = request.params.arguments?.readonly as boolean;
    
        if (readonly === undefined) {
          throw new Error("readonly parameter is required");
        }
    
        connectionConfig.readonly = readonly;
    
        return {
          content: [
            {
              type: "text",
              text: `Read-only mode ${readonly ? "enabled" : "disabled"}`
            }
          ],
          isError: false
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text:
                error instanceof Error
                  ? error.message
                  : "Unknown error occurred"
            }
          ],
          isError: true
        };
      }
    }
  • src/index.ts:259-273 (registration)
    Registration of the 'set_readonly' tool in the ListTools response, including its name, description, and input schema definition.
    {
      name: "set_readonly",
      description: "Enable or disable read-only mode",
      inputSchema: {
        type: "object",
        properties: {
          readonly: {
            type: "boolean",
            description:
              "Set to true to enable read-only mode, false to disable"
          }
        },
        required: ["readonly"]
      }
    }
  • Input schema for the 'set_readonly' tool, defining a required boolean 'readonly' parameter.
    inputSchema: {
      type: "object",
      properties: {
        readonly: {
          type: "boolean",
          description:
            "Set to true to enable read-only mode, false to disable"
        }
      },
      required: ["readonly"]
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Enable or disable read-only mode' implies a mutation that changes system state, it doesn't specify critical details like required permissions, whether the change is reversible, side effects (e.g., on active queries), or error conditions. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 a single, efficient sentence that directly states the tool's function without any fluff. It's appropriately sized and front-loaded, making it easy to parse quickly. Every word earns its place, with no wasted information.

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 (a mutation affecting system state), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what happens after enabling/disabling (e.g., confirmation message, error handling), nor does it cover behavioral aspects like permissions or side effects. For a state-changing tool, this leaves too much unspecified.

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?

The input schema has 100% description coverage, with the parameter 'readonly' clearly documented in the schema as a boolean to enable/disable mode. The description doesn't add any meaning beyond what the schema provides (it only restates the tool's purpose), so it meets the baseline of 3 where 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 with a specific verb ('Enable or disable') and resource ('read-only mode'), making it immediately understandable. However, it doesn't differentiate this tool from its siblings (like 'connect', 'disconnect', 'status') which might also affect system states, so it doesn't fully distinguish itself from alternatives.

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 prerequisites (e.g., needing to be connected first), exclusions, or how it relates to sibling tools like 'status' (which might show current mode) or 'disconnect' (which might affect access). Without such context, an agent might struggle to apply it correctly.

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

Related 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/sussa3007/mysql-mcp'

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