Skip to main content
Glama
MCP Dokploy Online
by igoruam

security-update

Idempotent

Updates the username and password for a specified Dokploy security configuration by security ID.

Instructions

POST /security.update

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": {
      "securityId": "<securityId>",
      "username": "<username>",
      "password": "<password>"
    },
    "name": "security-update"
  }
}

Input Schema

NameRequiredDescriptionDefault
passwordYes
usernameYes
securityIdYes

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 supply openWorldHint and idempotentHint, so safety/idempotency is partly covered and the description does not contradict them. However, it discloses nothing extra: not whether the update is partial or full replacement, not whether credentials in the payload grant access, and it omits destructiveHint for what is clearly a mutation.

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 technically short, but that brevity is under-specification rather than discipline. A single route string carries no front-loaded purpose, scope, or constraints for the agent to act on.

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?

This is a mutation endpoint with three undocumented required parameters, no output schema, and only partial annotations. The description should carry the full burden here and instead provides a bare HTTP route, leaving the agent unable to call it correctly without guessing.

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 required parameters (securityId, username, password) have 0% schema description coverage, so the schema does the minimum and the description compensates with nothing. Critically, it never clarifies whether username/password are caller credentials, target credentials, or values being written to the security object.

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 tool name and HTTP verb: 'POST /security.update' adds nothing beyond 'security-update'. It does not say what a 'security' object is (WAF rule, security group, firewall policy) or which fields the update changes.

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?

No when-to-use guidance is given at all, and no distinction from the visible siblings security-create, security-delete, and security-one. The only implied instruction is 'this is the update endpoint', which the agent could infer 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