Skip to main content
Glama
MCP Dokploy Online
by igoruam

previewDeployment-all

Read-onlyIdempotent

Fetches all preview deployments for a specified application, enabling you to review and manage preview environments in Dokploy.

Instructions

GET /previewDeployment.all

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": {
      "applicationId": "<applicationId>"
    },
    "name": "previewDeployment-all"
  }
}

Input Schema

NameRequiredDescriptionDefault
applicationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, and the 'GET' fragment is consistent with that read-only profile, so there is no contradiction. However the description adds no behavioral context of its own — nothing about permission/auth needs, result volume, pagination, or ordering — so it contributes nothing beyond the structured fields.

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 and front-loaded, but the brevity comes from under-specification rather than economy. The one line present conveys essentially no information an agent could act on.

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?

There is no output schema, no annotation explanation, and no description text, so the agent cannot know what the response contains, whether results are paginated, or how the applicationId constrains the listing. For a tool returning an unbounded 'all' collection this leaves every operational question unanswered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required parameter 'applicationId', so the description must carry that meaning and does not. It never says the parameter scopes the listing to one application, nor what format the identifier takes, leaving the agent to infer from the parameter name alone.

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 raw route string "GET /previewDeployment.all", which restates the tool name in HTTP form rather than describing the action. It hints at a read of all preview deployments, but never states what a preview deployment is, what 'all' scopes over, or how it differs from previewDeployment-one or deployment-all.

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 sibling alternative, despite a crowded family of previewDeployment-* and deployment-* tools. An agent has nothing to route on other than the name itself.

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