Skip to main content
Glama
MCP Dokploy Online
by igoruam

patch-one

Read-onlyIdempotent

Fetch details for a specific patch by its ID to inspect its stored information.

Instructions

GET /patch.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": {
      "patchId": "<patchId>"
    },
    "name": "patch-one"
  }
}

Input Schema

NameRequiredDescriptionDefault
patchIdYes

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, idempotentHint, and openWorldHint, so the safety profile is covered structurally. The description adds nothing beyond those annotations: it does not explain what the response contains, what happens when the ID is unknown, or what 'openWorld' means in this context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One fragment with no prose is technically brief, but brevity here is under-specification rather than conciseness. There is no front-loaded purpose statement for the agent to anchor 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?

No output schema exists, so the description should say something about return shape, yet it says nothing. With one undocumented parameter and no return information, the definition is too thin for an agent to call correctly even for a simple lookup.

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 patchId parameter, and the description does not compensate at all; it gives no format, source, or example for the identifier. An agent must guess whether patchId is a numeric ID, a slug, or a composite key.

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.one", which restates the tool name and HTTP method without saying what a 'patch' is or what the operation returns. An agent learns only that it is a fetch of one entity, and gets no distinguishing detail versus siblings such as patch-byEntityId or patch-create.

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 or when-not-to-use guidance, and no mention of the sibling patch-byEntityId that appears to be the alternative lookup path. The only implied guidance comes from the name itself, which suggests retrieving a single patch by 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