Skip to main content
Glama
MCP Dokploy Online
by igoruam

scim-listProviders

Read-onlyIdempotent

Retrieves the SCIM identity providers configured in Dokploy so administrators can review available identity provisioning connections.

Instructions

GET /scim.listProviders

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "scim-listProviders"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, and the GET verb in the description is consistent with a safe read. However, the description adds nothing beyond that: no note on pagination, result shape, whether providers span configured SSO/SCIM integrations, or any auth scope required for the SCIM endpoint.

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 that brevity comes from under-specification rather than efficiency — the only content is an HTTP route, which conveys less than the tool name does. Nothing is front-loaded because nothing explanatory is present.

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?

Although this is a simple zero-parameter read with no output schema, the description still fails to say what a 'provider' is in this context or what the response contains, which matters given multiple look-alike listProviders siblings. It is not wrong, just empty of substance.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters and the schema is an empty object with additionalProperties=false, so there is no parameter meaning for the description to supply. The baseline for a parameterless tool applies.

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 string "GET /scim.listProviders", which restates the tool name rather than explaining it. An agent can guess this lists SCIM identity providers, but the description never says so with a verb+resource statement and gives no basis for distinguishing it from sibling listProviders tools such as forwardAuth-listProviders or sso-listProviders.

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 tool, when not to, or which sibling to prefer. Since several sibling tools also list providers (forwardAuth, sso, ai-getCustomProviders), the absence of any routing guidance leaves the agent to infer selection from the tool 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