Skip to main content
Glama
MCP Dokploy Online
by igoruam

network-networksToSync

Read-onlyIdempotent

Retrieves the list of networks that need syncing for a specified server, so you can identify and reconcile network changes in Dokploy.

Instructions

GET /network.networksToSync

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-networksToSync"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIdNo

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=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that — no statement of what is returned, whether sync state is computed remotely, or what serverId scoping does.

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 short with no filler, but that brevity is under-specification rather than concision; there is no front-loaded statement of intent because there is no statement of intent at all.

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, a 0%-documented parameter, and no explanatory text, an agent has essentially nothing to decide correct invocation from. The definition is a bare route mapping, insufficient for a tool that likely returns syncable network state.

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% and the single parameter serverId is completely undocumented in both schema and description. The endpoint path hints at the network resource domain, but nothing explains what serverId filters or what happens when it is omitted (it is optional).

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 nothing but the raw endpoint string "GET /network.networksToSync", which restates the tool name in HTTP form rather than explaining what the operation does. It conveys the verb GET (a read) but leaves the meaning of "networksToSync" — what it returns and in what state — undefined.

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 guidance whatsoever on when to call this versus close siblings like network-all, network-one, or network-resync. An agent must guess from the names alone whether this lists syncable networks, triggers a sync, or checks sync status.

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