Skip to main content
Glama
MCP Dokploy Online
by igoruam

network-all

Read-onlyIdempotent

Retrieve all networks for a specified Dokploy server to inspect connectivity options before deploying or configuring services.

Instructions

GET /network.all

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": "network-all"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/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 externally. The description adds nothing beyond the verb — no mention of pagination, result volume, or what 'all' means across servers.

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 with no padding, but that brevity comes from under-specification rather than disciplined writing. The single fragment conveys almost no actionable information and is not front-loaded with intent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With one undocumented optional parameter, no output schema, and no explanation of scope, the definition leaves the agent guessing about both input effect and expected results. Annotations cover read-only safety but nothing about the tool's data semantics.

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?

There is one optional parameter (serverId) with 0% schema description coverage, and the description never mentions it. The agent gets no signal about whether serverId narrows the listing or what omitting it returns.

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 'GET /network.all' — an HTTP verb plus the resource path, which effectively restates the tool name 'network-all'. An agent can infer it lists networks, but there is no stated scope, return shape, or distinction from siblings like network-one or network-inspect.

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, when-not-to-use, or alternative routing is provided. Nothing tells an agent whether to prefer this over network-one, network-inspect, or network-networksToSync for a given goal.

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