Skip to main content
Glama
MCP Dokploy Online
by igoruam

mariadb-one

Read-onlyIdempotent

Fetches details for a specific MariaDB database instance by ID, helping you inspect its configuration and status in Dokploy.

Instructions

GET /mariadb.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": {
      "mariadbId": "<mariadbId>"
    },
    "name": "mariadb-one"
  }
}

Input Schema

NameRequiredDescriptionDefault
mariadbIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the description could focus on what a lookup returns or what happens on a missing ID. It adds nothing beyond the annotations — no error behavior, no auth requirements, no payload shape.

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 short by virtue of under-specification rather than economy; a bare HTTP route is not a front-loaded explanation of intent.

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?

A single-resource read tool with one required, undocumented parameter, no output schema, and a description that conveys no semantics — the definition is not complete enough to invoke confidently.

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% and the description says nothing about mariadbId, so an agent gets no signal that this is the identifier of the instance to fetch, nor any format expectations.

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 /mariadb.one" only restates the route implied by the tool name; it never says it retrieves a single MariaDB instance's details. An agent cannot distinguish it from mariadb-search or the other mariadb-* siblings from this text alone.

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 mention of the required ID lookup, and no reference to any alternative sibling such as mariadb-search for listing or ai-one/application-one for other resource types.

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