Skip to main content
Glama
MCP Dokploy Online
by igoruam

patch-readRepoDirectories

Read-onlyIdempotent

Reads repository directory contents for a specified Dokploy application or compose project, letting you inspect repo structure before deployment or configuration changes.

Instructions

GET /patch.readRepoDirectories

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": {
      "id": "<id>",
      "type": "<type>",
      "repoPath": "<repoPath>"
    },
    "name": "patch-readRepoDirectories"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
typeYes
repoPathYes

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=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered elsewhere. The only added signal is the "GET" prefix, which merely echoes readOnlyHint; nothing is said about remote repo access implications despite openWorldHint, nor about failure modes or return shape.

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 only one fragment, so there is no bloat, but that brevity comes from under-specification rather than economy. The route string is not front-loaded useful information for an agent deciding whether to call it.

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 three required undocumented parameters, no output schema, and no annotations explaining semantics, the description provides no compensating detail. An agent cannot confidently construct a valid call from this alone.

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?

All three parameters (id, type, repoPath) are required with 0% schema description coverage, so the description carries the full burden — and it says nothing. The meaning of the enum values "application" vs "compose" and the expected repoPath format are left entirely unexplained.

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 only restates the tool name as an HTTP route ("GET /patch.readRepoDirectories"), which is a tautology rather than an explanation. It never says what a "repo directory" read returns or how it differs from siblings like settings-readDirectories or patch-readRepoFile.

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 prerequisites, and no mention of any alternative tool. An agent has no basis for choosing this over patch-readRepoFile or settings-readDirectories.

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