Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-readDirectories

Read-onlyIdempotent

Retrieves configured directories for a specific Dokploy server, enabling you to review storage and deployment path settings.

Instructions

GET /settings.readDirectories

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": "settings-readDirectories"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIdNo

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 declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that — no indication of what is read, whether results are scoped to a server, or how the open-world behavior manifests. There is no contradiction with the annotations, but no added context either.

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 single line is not padded, but it is under-specified rather than concise — it spends its only words echoing the tool name and schema route instead of front-loading any explanatory content.

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?

With no output schema, an undocumented optional parameter, and a description that is just an endpoint string, an agent cannot predict what this returns or how to scope the call. For a read tool this is thin, even though the risk of misuse is low.

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 optional serverId parameter, so the description carries the full burden and delivers nothing. It does not say what a serverId means here, whether omitting it returns directories across all servers, or what form the identifiers take.

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 "GET /settings.readDirectories", which restates the tool name as an HTTP route. It never says what these directories are (repo directories? server settings paths?), what they contain, or how the result differs from the sibling patch-readRepoDirectories or the other settings-read* tools.

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, no prerequisites, and no mention of any alternative. The embedded "read" verb weakly implies a retrieval operation, but the agent is given nothing about when this tool is the right choice versus the many settings-read* siblings.

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