Skip to main content
Glama
MCP Dokploy Online
by igoruam

mounts-allNamedByApplicationId

Read-onlyIdempotent

Retrieves all named mounts for a Dokploy application using its application ID, so you can inspect configured mounts before deployment or troubleshooting.

Instructions

GET /mounts.allNamedByApplicationId

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": {
      "applicationId": "<applicationId>"
    },
    "name": "mounts-allNamedByApplicationId"
  }
}

Input Schema

NameRequiredDescriptionDefault
applicationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already supply readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds nothing beyond them: no indication of pagination, result shape, whether unnamed/anonymous mounts are excluded, or what happens if the application has no mounts.

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 a single line with no padding, but this is under-specification rather than conciseness. Nothing is front-loaded because there is no explanatory content to front-load.

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?

For a one-parameter, annotation-covered read tool this could be simple, but with no output schema and no parameter documentation the agent still cannot predict what comes back or how to use applicationId correctly. The definition supplies essentially zero of the remaining burden.

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 coverage is 0% and the sole required parameter applicationId is documented only by its name in the schema. The description adds no meaning — not even confirmation that this is the application identifier used for filtering, or any expected format.

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 /mounts.allNamedByApplicationId" restates the tool name as a raw HTTP route rather than describing an operation. It signals a read of mounts tied to an application, but never explains what "allNamed" means or what a mount record contains.

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 at all — nothing distinguishes this from siblings such as mounts-listByServiceId or mounts-one. The name implies filtering by applicationId, but the description states no conditions, prerequisites, or alternatives.

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