Skip to main content
Glama
MCP Dokploy Online
by igoruam

swarm-getNodeApps

Read-onlyIdempotent

Retrieves the applications running on a specific Docker Swarm node using its server ID, helping you inspect node workloads in Dokploy.

Instructions

GET /swarm.getNodeApps

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": "swarm-getNodeApps"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/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 safety is covered without the description. The description adds no behavioral context of its own, such as whether serverId is required in practice, what happens when it is omitted, or what scope of results is returned.

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, but this is under-specification rather than conciseness. A bare HTTP route is not a front-loaded explanation an agent can 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?

For a tool with an undocumented parameter and no output schema, the definition provides nothing beyond the route. An agent cannot tell what it returns or how to call it correctly when serverId is omitted.

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

Parameters1/5

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

The single parameter serverId has 0% schema description coverage, and the description does not compensate at all. It does not say what serverId identifies, whether it can be omitted, or what happens by default.

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 endpoint string "GET /swarm.getNodeApps", which restates the tool name rather than explaining the purpose. Nothing says what a 'node app' is or what listing them yields.

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 reference to sibling tools such as swarm-getNodes or swarm-getNodeInfo. An agent has to infer everything from 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