Skip to main content
Glama
Sign In

MySQL MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

mysql Data

query_data
Read-only

Query mysql data (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id, connection_slug AND available_actions

  2. request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] - Get detailed body structure for specific action(s) using actions from available_actions

IMPORTANT: Always call step 2 to see the exact body structure before querying.

query_data accepts read-only SQL only: a single SELECT (or EXPLAIN) statement. Write statements (INSERT/UPDATE/DELETE/DDL) are rejected here - send them through execute_action.

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": {
      "body": "<body>"
    },
    "name": "query_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the read-only claim is partly redundant, though the description usefully specifies the enforcement detail (single SELECT/EXPLAIN only, INSERT/UPDATE/DELETE/DDL rejected) and offers the correct escape hatch. It says nothing about result-set limits, timeouts, or what the returned data looks like for a potentially large query, which are the real behavioral risks here.

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?

Well front-loaded: the tool's role and workflow position appear in the first line, prerequisites are numbered, and the read-only constraint is bolded. Slightly repetitive in restating 'Always call step 2' after the numbered list, but no sentence is genuinely wasted.

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?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. The remaining gap is the nested, undocumented body object — the description tells the agent where to learn its shape but not what it looks like, which leaves a real hole before first invocation.

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

Parameters2/5

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

Schema coverage is 0% and the single parameter is an opaque object with additionalProperties: true, so an agent has no idea what keys the body expects. The description only hints that SQL is the payload and deflects to query_contexts for 'the exact body structure' — redirecting to another tool is not the same as documenting the parameter, though at least it prevents blind guessing.

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?

States a specific verb and resource ('Query mysql data') and immediately constrains it to read-only SQL. It explicitly distinguishes itself from both siblings: query_contexts as the prerequisite discovery step and execute_action as the destination for write statements.

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

Usage Guidelines5/5

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

Gives an explicit ordered workflow ('REQUIRED: Complete these steps first'), names the exact requests and parameters to run first, and states the exclusion rule: writes are rejected here and must go through execute_action. Nothing about when to pick this tool is left to inference.

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

All MySQL MCP by InsightfulPipe toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources