Skip to main content
Glama
MCP Dokploy Online
by igoruam

forwardAuth-serverStatus

Read-onlyIdempotent

Checks the Dokploy server status through the forward-authentication endpoint so you can verify the instance is reachable and responding.

Instructions

GET /forwardAuth.serverStatus

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "forwardAuth-serverStatus"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered by structured data. The description adds nothing beyond that – no note on what the status reflects, whether it hits a live server, or what a failure looks like.

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?

The single line is short but not concise in a useful sense – it is an under-specified route string rather than a front-loaded explanation. Brevity here reflects missing content rather than economy of wording.

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?

With no output schema and no parameters, the description carries the burden of explaining what 'serverStatus' returns, yet it gives none of that. Annotations cover the safety hints, but the agent still lacks any behavioral detail needed to interpret results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics for the description to explain. This meets the baseline-4 expectation for parameterless tools despite the absent prose.

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 only restates the HTTP route 'GET /forwardAuth.serverStatus', which is essentially a tautology of the tool name. It does not say in prose what the tool actually does or what kind of status it returns, so an agent must infer purpose entirely from the name.

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 tool versus siblings like forwardAuth-status or server-one. The description gives no context, prerequisites, or alternatives, leaving routing decisions to the agent's inference from the 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