Skip to main content
Glama
MCP Dokploy Online
by igoruam

scim-deleteProvider

Destructive

Delete a SCIM provider by its providerId in Dokploy to remove identity provisioning access and clean up unused SCIM configurations.

Instructions

POST /scim.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": "scim-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 write/destructive nature is known. The description adds nothing about what is destroyed (provider config only, or also linked identities and tokens), whether the action is reversible, or what the response is, which is a substantial gap for an irreversible delete.

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 terse, but this is under-specification rather than conciseness; the single line is a route stub with no front-loaded purpose statement. No sentence earns its place because the only sentence merely echoes the name.

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?

A destructive single-parameter mutation with no output schema and no annotations beyond destructiveHint requires the description to explain target semantics and effects. Nothing is provided beyond the HTTP verb and path.

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 providerId parameter, so the description carries the full burden of explaining it and provides nothing. It does not say whether providerId is an internal ID, a SCIM provider slug, or an IdP entity ID.

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 raw route "POST /scim.deleteProvider", which restates the tool name rather than stating what the operation actually does. An agent can infer a deletion of a SCIM provider from the name, but the description contributes nothing beyond that inference.

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 how this differs from sibling tools such as sso-deleteProvider or scim-listProviders. The agent is left to guess entirely from the name.

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