Skip to main content
Glama
MCP Dokploy Online
by igoruam

redirects-create

Creates a redirect rule for a Dokploy application using a regex pattern, replacement URL, and permanent flag.

Instructions

POST /redirects.create

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

Input Schema

NameRequiredDescriptionDefault
regexYes
permanentYes
replacementYes
applicationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

The only annotation is openWorldHint=true, so the description carries the full behavioral burden and supplies nothing: no statement about permissions, conflict behavior with existing rules, whether creation is idempotent, or what a successful response contains. A mutation endpoint described only by its HTTP verb gives the agent no basis to predict side effects.

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 brevity reflects under-specification rather than efficiency; there is no front-loaded statement of purpose or scope. The one line present duplicates information already available in the tool name.

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 four-parameter required-field mutation tool with no output schema and near-zero annotation coverage, the description provides no usable context. Everything an agent needs to call this correctly must be guessed from parameter names.

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% across four required parameters (regex, replacement, permanent, applicationId), and the description adds no meaning for any of them. Key ambiguities — the dialect of the regex, the form of the replacement target, and what permanent changes in the runtime — remain entirely undocumented.

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 "POST /redirects.create", which merely restates the tool name in HTTP-path form. It does not explain what a redirect consists of, what the rule does at runtime, or how it differs from redirects-update 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 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 the closely related siblings redirects-update, redirects-one, and redirects-delete. The agent must infer everything about selection from the tool name alone.

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