Skip to main content
Glama
MCP Dokploy Online
by igoruam

redis-saveExternalPort

Idempotent

Configure or clear the external port for a Redis instance by ID to control external access in Dokploy.

Instructions

POST /redis.saveExternalPort

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": {
      "redisId": "<redisId>",
      "externalPort": "<externalPort>"
    },
    "name": "redis-saveExternalPort"
  }
}

Input Schema

NameRequiredDescriptionDefault
redisIdYes
externalPortYes

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 supply openWorldHint=true and idempotentHint=true, so the basic safety profile is covered, but the description adds nothing beyond them. For a write-style operation it never says what externalPort represents, whether a port must be pre-allocated, whether the change disrupts the running instance, or whether it is reversible.

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 brevity here comes from under-specification rather than efficiency; the single route string conveys no task-relevant information and is not front-loaded with purpose.

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 two-parameter mutation tool with no output schema, no parameter documentation, and only hint-level annotations needs a real description. Nothing about the effect, required permissions, or result of the call is provided.

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?

Both parameters (redisId, externalPort) have 0% schema description coverage, so the description carries the full burden of explaining them and explains neither. It does not clarify the redis identifier format, the allowed port range, or why externalPort is nullable.

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 "POST /redis.saveExternalPort", which restates the tool name as an HTTP route rather than stating in plain language what the operation does (e.g., assign an externally reachable port to a Redis instance). It gives no differentiation from the many sibling *-saveExternalPort tools beyond the route prefix.

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 guidance on when to use this versus port-create, port-update, or the sibling database variants. An agent must infer the intended context entirely from the tool name, and no prerequisites or exclusions are stated.

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