Skip to main content
Glama
MCP Dokploy Online
by igoruam

redirects-one

Read-onlyIdempotent

Retrieve details for a specific Dokploy redirect by ID so you can inspect or manage its configuration.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
redirectIdYes

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?

Annotations declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered structurally. The description adds nothing: no mention of what happens when the redirectId doesn't exist (404 vs empty), no auth or workspace-scoping requirements, no rate-limit or caching behavior for an open-world HTTP-backed call.

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?

Extremely short, but short by omission rather than by discipline. The raw route string is not front-loaded information an agent can act on; it is essentially a placeholder where a one-sentence purpose statement should be.

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 single-record lookup tool with zero annotation-level behavioral detail conveyed in prose, 0% parameter documentation and no output schema. The description leaves everything an agent would need to call it correctly unspecified.

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 the single required `redirectId` parameter, so the burden falls entirely on the description, which says nothing about it. It doesn't state whether the ID is a slug, numeric ID, or UUID, nor any format expectations.

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 literally "GET /redirects.one" – a raw HTTP method plus path, which restates the tool name rather than explaining the purpose. It never says it fetches a single redirect by ID, even though the required `redirectId` parameter strongly implies exactly that.

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?

No guidance whatsoever about when to use this versus siblings like redirects-create/update/delete, or when to prefer any list/search alternative. The only inference an agent can make is that 'one' implies a single-record fetch.

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