Skip to main content
Glama
MCP Dokploy Online
by igoruam

redis-search

Read-onlyIdempotent

Search and filter Redis services by name, query, project, app, or environment to locate instances within a Dokploy infrastructure and return paginated results.

Instructions

GET /redis.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": "redis-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, idempotentHint=true and openWorldHint=true, so the safety profile is covered elsewhere. The description adds nothing beyond that: no mention of pagination behavior, result ordering, or what happens with zero matches, so it contributes no behavioral context of its own.

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 string is short but that is under-specification rather than conciseness; there is no structure, no front-loaded intent, and no sentence that actually earns its place by informing the agent.

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?

An eight-parameter, zero-required search endpoint with no output schema requires the description to explain filtering semantics, result shape, and pagination. The description is a bare route string and covers none of this, leaving the definition inadequate for correct invocation.

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?

The schema documents eight parameters (q, name, limit, offset, appName, projectId, description, environmentId) at 0% description coverage. The description supplies no meaning for any of them — not even the distinction between free-text q and the exact-match name filter — so the gap is total.

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 /redis.search" only restates the tool name with an HTTP method prefixed. It conveys that something is retrieved about Redis, but never says whether it searches Redis instances, keys, configs, or logs, nor what distinguishes it from the many sibling *-search tools.

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 prerequisites, and no mention of alternatives such as redis-one for fetching a specific instance. An agent has no basis for choosing this tool over its siblings.

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