Skip to main content
Glama
MCP Dokploy Online
by igoruam

network-inspect

Read-onlyIdempotent

Retrieve detailed configuration and status for a Dokploy network by ID to verify settings and troubleshoot connectivity issues.

Instructions

GET /network.inspect

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": {
      "networkId": "<networkId>"
    },
    "name": "network-inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkIdYes

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?

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds no behavioral context of its own — no indication of cost, latency, whether the target must exist, or what the operation returns.

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 this is under-specification rather than conciseness. A raw route string is not a description and leaves no front-loaded statement of intent for the agent to 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?

With no output schema and no parameter documentation, the description is the only place an agent could learn what comes back or how to call this correctly, and it provides none of it. Inadequate for even a one-parameter tool.

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%, so the description carries the burden for the single networkId parameter and fails to. It does not say whether the value is an internal ID, a slug, or a name, nor what happens with an unknown ID.

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?

"GET /network.inspect" only restates the tool name in HTTP-endpoint form. It implies a read against a network resource but never says what is inspected (config, connectivity, health) or how it differs from siblings like network-one or network-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 exclusion, and no reference to any alternative. An agent choosing between network-inspect, network-one, and network-all gets nothing to discriminate on.

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