Skip to main content
Glama
MCP Dokploy Online
by igoruam

security-one

Read-onlyIdempotent

Fetches security details by security ID from a Dokploy instance, helping you inspect security settings and configuration.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
securityIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/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 them: no note on missing-resource behavior, auth requirements, or what the call returns, leaving the agent with a bare endpoint string.

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 short with no filler, but this is under-specification rather than conciseness: a single HTTP route line carries no front-loaded purpose, scope, or usage context.

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 tool with a required identifier and no output schema, the description supplies none of the information an agent needs: what the record contains, what happens on an unknown ID, or how the ID is shaped. The definition is effectively an empty shell.

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 securityId, and the description does not compensate by explaining its format, scope, or source. The parameter name is self-descriptive enough to avoid a 1, but the definition adds no meaning beyond the schema key.

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 /security.one" merely restates an HTTP method and a resource path; it implies retrieval of a single security resource only via the "-one" naming convention shared with siblings. It never states what a security resource is or what is returned, so an agent must guess from the name alone.

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 guidance on when to use this versus security-create/security-update or the other "-one" readers. No prerequisites, no exclusions, no indication of what identifier to supply or where to obtain it.

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