Skip to main content
Glama
MCP Dokploy Online
by igoruam

overview-services

Read-onlyIdempotent

Fetches a summary of services from your Dokploy instance to monitor deployment status and infrastructure health.

Instructions

GET /overview.services

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": "overview-services"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/5.0
Behavior1/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 fully covered by structured data. The description adds nothing beyond that: no scope of the overview, no indication of whether it aggregates across servers/projects, and no sense of the response shape. For an open-world endpoint with no output schema, this is a pure endpoint restatement.

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 minimal but that is under-specification rather than conciseness. A single endpoint token is not front-loaded information the agent can act on, and 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?

With no output schema and an openWorldHint, the description is the only channel for explaining what this endpoint surfaces and at what granularity. It provides none of that, so an agent cannot tell what it will receive or how to interpret it relative to the other overview-* tools.

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

Parameters4/5

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

The input schema has zero properties (additionalProperties: false), so there are no parameters whose semantics could be clarified. Baseline 4 applies; there is nothing for the description to add or omit on this dimension.

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 entire description is "GET /overview.services", which restates the tool name as an HTTP method plus path. It conveys only that a read occurs against something called 'overview.services', without saying what a 'service' is in this context or what information is returned. It does not distinguish itself from siblings like overview-backups, overview-domains, compose-loadServices, or server-getServices.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/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 stated preconditions, and no mention of any alternative such as compose-loadServices or server-getServices. The agent is left to guess whether this is a status summary, a service inventory, or a health overview, and must rely on 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