Skip to main content
Glama
MCP Dokploy Online
by igoruam

redirects-update

Idempotent

Update a Dokploy redirect rule by ID, including its regex pattern, replacement target, and permanent status.

Instructions

POST /redirects.update

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": {
      "redirectId": "<redirectId>",
      "regex": "<regex>",
      "replacement": "<replacement>",
      "permanent": "<permanent>"
    },
    "name": "redirects-update"
  }
}

Input Schema

NameRequiredDescriptionDefault
regexYes
permanentYes
redirectIdYes
replacementYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare openWorldHint=true and idempotentHint=true, so the safety/idempotency profile is covered structurally. The description adds nothing: it does not say whether regex and replacement fully overwrite existing values, whether the whole redirect is replaced, what permissions are required, or what the response contains for a mutation tool.

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 short because it is under-specified, not because it is efficient. A raw endpoint path is not useful front-loaded content for an agent.

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?

A four-parameter write operation with zero description coverage in the schema and no output schema needs substantial explanation of parameters and effects. The description supplies none, so an agent cannot call this tool correctly without guessing.

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% and all four parameters (redirectId, regex, replacement, permanent) are required, so the description carries the full burden of explaining them. It says nothing about any of them, leaving an agent to guess at format and semantics for unlabeled fields.

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 the route signature 'POST /redirects.update', which essentially restates the tool name. An agent can infer this modifies an existing redirect, but there is no plain-language statement of what is updated or how, and no differentiation from siblings like redirects-create or redirects-one.

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?

No when-to-use guidance, no prerequisites, and no mention of when to choose redirects-create or redirects-one instead. The only usage signal available is the 'update' verb embedded in the name, which is weak inference rather than guidance.

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