Skip to main content
Glama
MCP Dokploy Online
by igoruam

security-create

Creates application-level security credentials by assigning a username and password to a specified Dokploy application ID for access control.

Instructions

POST /security.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": {
      "applicationId": "<applicationId>",
      "username": "<username>",
      "password": "<password>"
    },
    "name": "security-create"
  }
}

Input Schema

NameRequiredDescriptionDefault
passwordYes
usernameYes
applicationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

The only behavioral signal is 'POST', which weakly implies a mutating write, plus an openWorldHint annotation. With no readOnly/destructive hints supplied, the description should disclose whether the created credential is retrievable later, whether it requires elevated permissions, and whether the operation is idempotent — none of which appears.

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 text is short but that is under-specification rather than concision; a bare HTTP route fragment is not front-loaded useful information. Nothing in the single fragment earns its place beyond echoing 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 mutation tool handling a password credential with three undocumented required parameters, no output schema, and near-empty annotations, the description is completely inadequate. An agent has no basis to construct a correct call.

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?

All three parameters (applicationId, username, password) are required with 0% schema description coverage, so the description is the only place semantics could be explained. It says nothing about any of them — not whether applicationId references an existing application, nor what username means in this context, nor any password constraints.

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 just 'POST /security.create', which restates the tool name and HTTP route without stating what resource is created. An agent cannot tell from this whether it creates a credential, a security policy, or an SSH key, nor how it differs from siblings like security-update or server-security.

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-update or security-one. The agent must guess entirely from the name.

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