Skip to main content
Glama
Sign In

MySQL MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

mysql Setup Helper

query_contexts
Read-only

Helper for planning InsightfulPipe mysql requests.

Step 1: request='accounts' – Retrieve workspace_id, brand_id, connection_slug, other source metadata, AND available_actions (all read-only actions you can call).

Step 2: request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] – REQUIRED before querying. Replace with actions from available_actions to get the exact request body, required identifiers, fields, and notes for each action.

Optional: request='available_actions' – Standalone call to list all available actions (already included in accounts response).

Optional: request='brands' with brand_id + workspace_id to pull brand guidelines.

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": {
      "request": "<request>"
    },
    "name": "query_contexts"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionsNo
requestYes
brand_idNo
platformNo
workspace_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond readOnlyHint=true, it discloses important dependencies: actions_details is required before querying, available_actions is already included in accounts, and brands needs brand_id plus workspace_id. It does not discuss auth, limits, or failure behavior, but annotations already cover the safety profile and output schema covers returns.

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 front-loaded and organized as Step 1, Step 2, and optional calls. Each line adds actionable context, including the useful note that available_actions is redundant with accounts.

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 five-parameter discovery tool with an output schema, the workflow is nearly complete: it covers the required setup path and the main optional calls. The notable gap is the undocumented platform parameter.

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 0%, so the description must carry parameter meaning. It explains request modes, the actions list for actions_details, and brand_id/workspace_id for brands, but it does not explain the platform parameter at all.

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 states a specific role: a helper for planning InsightfulPipe mysql requests, with enumerated discovery modes. It distinguishes itself from execution/query siblings by framing this as the required setup/discovery step before querying.

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?

It gives explicit sequencing: call request='accounts' first, then request='actions_details' with actions before querying. It also marks available_actions and brands as optional and explains when each is useful.

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