Skip to main content
Glama
MCP Dokploy Online
by igoruam

compose-search

Read-onlyIdempotent

Search Docker Compose services by name, description, query, app name, project, or environment. Filter and paginate results to find the compose stack you need.

Instructions

GET /compose.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": "compose-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.3/5.0
Behavior1/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the baseline bar is low, yet the description adds nothing beyond them — no pagination behavior, no matching semantics, no note on which fields are OR/AND combined. "GET" merely echoes the readOnly annotation rather than adding context.

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 certainly short, but the brevity is under-specification rather than conciseness. A single route string is not a front-loaded description of behavior; there is 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 an 8-parameter search endpoint with no output schema and no annotation detail on results, this definition is far too thin. An agent cannot determine match semantics, pagination defaults, or result shape from the definition alone.

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?

Eight parameters with 0% schema description coverage and no enum or format hints, and the description supplies zero meaning for any of them. Critical ambiguities — whether q is a full-text query, whether name/description are substring or exact filters, what appName/environmentId scoping does, and the limit/offset pagination contract — are left completely 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 the raw HTTP route "GET /compose.search", which restates the tool name rather than explaining what it does. An agent can infer it searches Compose resources and is a read operation, but nothing about what is searched, what is returned, or how it differs from compose-one or the other *-search siblings is conveyed.

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 exclusions, and no mention of any alternative. With siblings like project-search, application-search, and compose-one present, guidance is essential and entirely absent.

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