Skip to main content
Glama
MCP Dokploy Online
by igoruam

sso-update

Idempotent

Update an existing SSO provider configuration in Dokploy, setting issuer, domains, and OIDC or SAML details for authentication.

Instructions

POST /sso.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": {
      "providerId": "<providerId>",
      "issuer": "<issuer>",
      "domains": "<domains>"
    },
    "name": "sso-update"
  }
}

Input Schema

NameRequiredDescriptionDefault
issuerYes
domainsYes
oidcConfigNo
providerIdYes
samlConfigNo
organizationIdNo
overrideUserInfoNo

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?

Annotations supply openWorldHint and idempotentHint, but the description adds nothing beyond the endpoint path. It does not say whether the update replaces the entire provider config (the required providerId/issuer/domains suggest a full write), what permissions are needed, or what happens to existing OIDC/SAML settings not supplied.

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, but the brevity here is under-specification rather than efficiency: a bare verb-and-path line with no front-loaded statement of effect or scope. Nothing is wasted because nothing is said.

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 high-complexity mutation tool with a deeply nested schema, three required parameters, and no output schema, the definition provides essentially no information needed to call it safely or correctly.

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?

Schema description coverage is 0% across seven parameters, including deeply nested oidcConfig, samlConfig, and spMetadata/idpMetadata objects. The description contributes no meaning for any of them, leaving required vs optional fields, mutual exclusivity of OIDC vs SAML config, and default semantics undocumented.

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 route 'POST /sso.update', which restates the tool name rather than describing the resource or effect. An agent can guess it mutates SSO provider configuration, but nothing distinguishes it from siblings like sso-updateTrustedOrigin or settings-updateEnforceSSO.

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 any alternative tool. The agent is left to infer usage entirely from the tool name and the presence of sibling SSO 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