Skip to main content
Glama
MCP Dokploy Online
by igoruam

mounts-one

Read-onlyIdempotent

Fetches details of a single Dokploy mount by its ID, letting you inspect its configuration and referenced resources before updating or troubleshooting it.

Instructions

GET /mounts.one

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": {
      "mountId": "<mountId>"
    },
    "name": "mounts-one"
  }
}

Input Schema

NameRequiredDescriptionDefault
mountIdYes

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 structurally. The description adds nothing: no error behavior (e.g., 404 on unknown mount), no note about what a mount record contains, no visibility or permission context.

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 technically concise, but brevity here reflects under-specification rather than density of information. A raw method-plus-path fragment is not a front-loaded explanation of a tool's behavior.

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 resource-fetch tool with zero schema description coverage and no output schema, the agent has no information about what comes back or how failures manifest. The definition is essentially an endpoint stub, far short of what is needed to call it confidently.

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% for the single required mountId, so the description is the only place semantics could be added—and it adds none (no format, source, or how to obtain a valid ID). The parameter name is largely self-explanatory, which keeps this above 1.

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 just "GET /mounts.one," which restates the tool name and HTTP method rather than explaining what it does. "one" hints at a single-resource fetch, but an agent gets no independent statement of purpose beyond the identifier.

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 on when to use this versus siblings such as mounts-allNamedByApplicationId or mounts-listByServiceId, nor any mention that it requires an existing mountId. Nothing indicates when-not to use it or what happens for an unknown ID.

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