Skip to main content
Glama
MCP Dokploy Online
by igoruam

mysql-search

Read-onlyIdempotent

Search MySQL database services and resources across Dokploy projects, environments, and applications by name, description, or query; use filters and pagination to find the target instance.

Instructions

GET /mysql.search

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mysql-search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNo
nameNo
limitNo
offsetNo
appNameNo
projectIdNo
descriptionNo
environmentIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered without the description's help. The description adds nothing further: no note on pagination behavior despite limit/offset, no indication of result shape or ordering, and no hint that openWorld search may reach external sources.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Brevity here is under-specification rather than economy; the single fragment is not a sentence and is not front-loaded with any actionable content. Nothing in it earns a place because it duplicates the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an eight-parameter search tool with no output schema and no parameter documentation, the description is wholly inadequate. An agent must guess the semantics of every filter and the pagination contract before it can call this correctly.

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

Parameters1/5

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

Schema description coverage is 0% across eight parameters, so the description carries the full burden and supplies none of it. Terms like q, name, appName, projectId, and description are ambiguous — the agent cannot tell which field is a free-text query versus an exact filter, nor how they combine.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"GET /mysql.search" only restates the tool name in HTTP-endpoint form; it says nothing about what a mysql search returns or matches against. An agent learns the resource (mysql) and the operation type (search) but nothing else, leaving it indistinguishable in substance from siblings like mariadb-search or mysql-one beyond the resource family.

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?

There is no guidance on when to use this versus mysql-one, mysql-readLogs, or the other *-search siblings. No preconditions, no exclusions, and no indication of what the eight optional filters are meant to select.

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

Deploy Server

Other Tools