Skip to main content
Glama
MCP Dokploy Online
by igoruam

server-security

Read-onlyIdempotent

Fetches security configuration for a Dokploy server by server ID, helping users audit access settings and infrastructure posture.

Instructions

GET /server.security

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": {
      "serverId": "<serverId>"
    },
    "name": "server-security"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIdYes

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 readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered structurally. The description adds nothing beyond that — no indication of what security configuration is returned, whether it requires elevated permissions, or whether results reflect live or cached state.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single token-efficient line with no filler, so nothing is wasted. However, brevity here is under-specification rather than concision — there is no front-loaded statement of intent to anchor the 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?

With no output schema and no description of the return value, an agent cannot know what a successful call yields. Combined with a 0%-documented parameter and no usage context, the definition is inadequate for a tool that exposes security configuration.

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

Parameters2/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 serverId parameter, so the description carries the burden of explaining it and does not. The name serverId is largely self-evident, which keeps this above a 1, but no format, source, or lookup guidance is offered.

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?

"GET /server.security" only restates an HTTP route; it conveys that the tool reads server security data but gives no statement of what the payload contains or how it differs from siblings like security-one or server-one. It is closer to a route dump than a purpose statement.

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 alternatives such as security-one or security-update. An agent has no basis for choosing this tool over the many adjacent security/server tools.

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