Skip to main content
Glama
MCP Dokploy Online
by igoruam

mounts-listByServiceId

Read-onlyIdempotent

Retrieve all mounts for a specific Dokploy service by providing its service type and ID to inspect configured storage volumes.

Instructions

GET /mounts.listByServiceId

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": {
      "serviceType": "<serviceType>",
      "serviceId": "<serviceId>"
    },
    "name": "mounts-listByServiceId"
  }
}

Input Schema

NameRequiredDescriptionDefault
serviceIdYes
serviceTypeYes

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 the safety profile is covered elsewhere; the description adds nothing about return shape, pagination, or what a missing service means. It does not contradict the annotations, but it contributes no behavioral context whatsoever.

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 brevity here comes from omission rather than discipline: a bare route string conveys nothing an agent could act on. There is no structure such as purpose, scope, or routing guidance.

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 two required undocumented parameters, no output schema, and no annotations explaining semantics, the description needed to carry substantial weight and instead carries none. An agent cannot reliably construct the serviceType value or interpret results from this definition.

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?

Schema description coverage is 0% for both required parameters, and the description supplies no meaning for serviceId or serviceType — not even their expected format or the allowed service types. The full burden of documenting these two required inputs is left unmet.

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 the HTTP route 'GET /mounts.listByServiceId', which restates the tool name and implies a read of mounts scoped to a service. It never states in plain language what the tool returns or how it differs from siblings like mounts-one or compose-loadMountsByService, so it is essentially a tautology of the endpoint.

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 prerequisite or exclusion, and no mention of any alternative tool. An agent has no basis for choosing this over mounts-one or compose-loadMountsByService from the definition 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