Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-updateEnforceSSO

Idempotent

Enable or disable enforced single sign-on for Dokploy instance settings by updating the required SSO enforcement flag.

Instructions

POST /settings.updateEnforceSSO

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": {
      "enforceSSO": "<enforceSSO>"
    },
    "name": "settings-updateEnforceSSO"
  }
}

Input Schema

NameRequiredDescriptionDefault
enforceSSOYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/5.0
Behavior2/5

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

Annotations only supply openWorldHint=true and idempotentHint=true; they say nothing about destructiveness or auth requirements. The description adds no behavioral context at all — not whether disabling enforcement affects existing sessions, who may call it, or whether it requires admin/enterprise licensing.

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 a single short string, but brevity here reflects under-specification rather than efficiency. A bare endpoint path is not front-loaded information an agent can 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?

For a security-sensitive settings mutation with one undocumented parameter, no output schema, and thin annotations, the definition provides essentially nothing beyond an HTTP route. An agent cannot confidently decide to call it or predict its effects.

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?

There is one required boolean parameter with 0% schema description coverage, so the description had to carry its meaning. It says nothing about what enforceSSO=true versus false does, leaving the agent to infer from the parameter name alone.

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 only the HTTP endpoint 'POST /settings.updateEnforceSSO', which restates the tool name rather than explaining what the tool does. There is no plain-language statement of effect (toggling SSO enforcement) or of how it differs from the sibling 'sso-enforceSSO'.

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, when-not-to-use, or alternative guidance is given. Given siblings such as 'sso-enforceSSO' and 'sso-update' that plausibly overlap, a routing hint was especially needed here.

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