Skip to main content
Glama
MCP Dokploy Online
by igoruam

environment-search

Read-onlyIdempotent

Search Dokploy environments by project ID, name, or description to locate deployment targets. Filter results with query terms, pagination, and limits for precise environment discovery.

Instructions

GET /environment.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": "environment-search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNo
nameNo
limitNo
offsetNo
projectIdNo
descriptionNo

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, idempotentHint and openWorldHint, so the safety profile is covered. The description contributes nothing beyond the verb GET, which merely echoes readOnlyHint; it says nothing about matching semantics, pagination defaults (limit 20, offset 0), or result ordering that an agent would need.

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 single bare HTTP route is not a front-loaded statement of purpose.

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?

Six undocumented parameters, no output schema, and no description of what a search returns. For a filtered search endpoint this is far from complete enough for reliable 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?

Six parameters with 0% schema description coverage, and the description explains none of them. It does not clarify whether q is a free-text query versus name/description being field-scoped filters, nor how projectId constrains results — the most important ambiguity for this tool.

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 only the HTTP route "GET /environment.search", which restates the tool name rather than defining the operation. A reader can infer it searches environments, but nothing says what an environment record is, what is matched, or how results are shaped.

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?

No when-to-use guidance, no prerequisites, and no mention of how this differs from the many sibling search tools (project-search, application-search) or from environment-one / environment-byProjectId. The agent must guess the routing entirely 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