Skip to main content
Glama
MCP Dokploy Online
by igoruam

patch-readRepoFile

Read-onlyIdempotent

Read a repository file for a specified Dokploy application or compose resource by ID and file path, enabling inspection of deployment configuration before changes.

Instructions

GET /patch.readRepoFile

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>",
      "filePath": "<filePath>"
    },
    "name": "patch-readRepoFile"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
typeYes
filePathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/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, and the "GET" wording is at least consistent with a read. Beyond that the description contributes nothing: no note on what happens for missing files, permissions required, or how openWorld access behaves.

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 that shortness reflects under-specification rather than economy, and the HTTP verb-plus-path form is not front-loaded with anything an agent can act on.

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 three required, undocumented parameters and no output schema, the definition leaves an agent guessing about the shape of a valid call. The annotations carry the read/idempotency story, but the description does not complete the picture.

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 three required parameters (id, type, filePath), and the description supplies no meaning for any of them. In particular, the application/compose enum on type and the format of filePath 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 is just "GET /patch.readRepoFile", which restates the tool name in HTTP-path form rather than stating in plain language what it does. It hints at a read of a repository file, but adds no verb meaning, scope, or differentiation from siblings such as patch-readRepoDirectories or patch-saveFileAsPatch.

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 alternatives. An agent cannot tell from this string when readRepoFile is appropriate versus the many other patch-* or container/file-reading 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