Skip to main content
Glama
MCP Dokploy Online
by igoruam

sso-listProviders

Read-onlyIdempotent

List configured SSO identity providers to identify available login options and configure authentication for Dokploy access.

Instructions

GET /sso.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": "sso-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?

The annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is carried by structured data. The description adds nothing behavioral beyond that — no mention of pagination, result size, auth requirements, or whether all providers or only SSO-configured ones are returned.

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 with no wasted words, but that brevity is under-specification rather than conciseness. There is no structure, no front-loaded purpose statement, and the single endpoint token conveys almost nothing.

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 simple zero-parameter read tool the bar is low, and annotations cover the safety profile, but the description still omits what the call returns (provider objects, fields, ordering) and there is no output schema to compensate. An agent cannot predict the result from this definition.

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 coverage is 100%, so there is nothing to document; the baseline for a no-parameter tool applies. No parameter semantics are needed or missing.

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 endpoint string "GET /sso.listProviders", which essentially restates the tool name. It does hint at a read/listing operation for SSO providers, but gives no scope, filter, or return-content detail that would distinguish it from the many sibling listProviders tools.

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 whatsoever. With siblings like scim-listProviders, forwardAuth-listProviders, and settings-updateEnforceSSO present, an agent gets no signal about which provider list this applies to or when to choose it.

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