Skip to main content
Glama
MCP Dokploy Online
by igoruam

sso-deleteProvider

Destructive

Deletes an SSO identity provider by providerId from Dokploy, removing its login configuration and stopping further authentication through that provider.

Instructions

POST /sso.deleteProvider

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>"
    },
    "name": "sso-deleteProvider"
  }
}

Input Schema

NameRequiredDescriptionDefault
providerIdYes

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 destructiveHint=true and openWorldHint=true, so the agent knows this is a destructive write. The description adds nothing beyond that—no indication of what is destroyed, whether dependent SSO configurations or trusted origins are also removed, whether confirmation or elevated permissions are required, or what the response reports. It does not contradict the annotations, but it contributes zero behavioral context.

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 one short fragment with no waste, but this is under-specification rather than conciseness. There is no front-loaded statement of purpose, no usage note, and nothing an agent can act on beyond the route string.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, irreversible operation with an undocumented required identifier and no output schema, the definition should explain target identification and consequences. The bare route leaves nearly every decision an agent must make before invoking this tool unaddressed.

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?

The single required parameter providerId has 0% schema description coverage, so the description carries the full burden of explaining it—and it says nothing. Whether providerId is an internal ID, a slug, or an external IdP identifier is completely undocumented, which is a serious gap for a destructive lookup-by-identifier tool.

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.deleteProvider", which restates the tool name rather than describing the operation. From name and path one can infer it deletes an SSO provider, but the text itself supplies no verb-plus-resource statement and gives no basis for distinguishing this from scim-deleteProvider or other delete siblings.

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 whatsoever on when to use this tool, what preconditions apply, or which sibling to prefer for related SSO operations. An agent must infer everything 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