Skip to main content
Glama
MCP Dokploy Online
by igoruam

mysql-one

Read-onlyIdempotent

Fetches a specific MySQL database by ID from Dokploy, letting you inspect its configuration and status for infrastructure management.

Instructions

GET /mysql.one

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": {
      "mysqlId": "<mysqlId>"
    },
    "name": "mysql-one"
  }
}

Input Schema

NameRequiredDescriptionDefault
mysqlIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/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 externally. The description adds nothing beyond that — no statement of what resource class 'mysql' represents, what happens when mysqlId is unknown, or what a call returns.

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?

It is short, but shortness here is under-specification rather than conciseness — a bare HTTP verb plus path with no front-loaded explanation of purpose or scope. Nothing is wasted because almost nothing is said.

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 a read-by-id tool with one undocumented parameter and no output schema, the description leaves the agent unable to predict the return value or the resource being fetched. Completeness is effectively absent.

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% for the single required parameter mysqlId, so the description must compensate and it does not: it never mentions the identifier, its format, or where it comes from. The parameter name alone carries all meaning.

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?

The description is the raw route string "GET /mysql.one", which merely restates the tool name and the readOnly annotation. The word "one" hints at fetching a single record by identifier, but no verb+resource statement confirms that, and nothing distinguishes it from siblings such as mysql-search or mysql-readLogs.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no condition for choosing this over mysql-search (list/filter) versus this tool's single-resource lookup, and no prerequisites or exclusions. An agent must infer everything from the name.

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