Skip to main content
Glama
MCP Dokploy Online
by igoruam

mariadb-search

Read-onlyIdempotent

Search MariaDB database services in Dokploy by name, app, project, or environment, using query filters and pagination to locate relevant instances.

Instructions

GET /mariadb.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": "mariadb-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.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and idempotentHint=true, so the safety profile is covered. The description adds nothing beyond that: no indication of result shape, pagination behavior via limit/offset, or whether the various filter fields combine with AND/OR semantics.

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?

The text is short but that is under-specification rather than concision; an endpoint echo conveys no usable information. There is no front-loaded statement of purpose and no structure to speak of.

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 tool with eight filter parameters, zero schema coverage and no output schema, the description is completely inadequate. An agent cannot call this tool correctly without guessing at parameter semantics and result behavior.

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, and the description supplies no meaning for any of them. The distinction between the free-text q, name, and description filters, plus the role of appName, projectId and environmentId, is entirely undocumented.

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 just "GET /mariadb.search", which restates the tool name and HTTP method rather than describing what the operation does. It hints at a search over MariaDB resources, but does not say what is searched or what is returned, and it does not distinguish this tool from siblings such as mysql-search or postgres-search.

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 guidance on when to use this tool, when to prefer a sibling search tool, or what prerequisites apply. The agent is left to infer everything from the name alone.

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