Skip to main content
Glama
MCP Dokploy Online
by igoruam

forwardAuth-listProviders

Read-onlyIdempotent

Lists configured forward authentication providers, helping you review and choose the correct provider for securing Dokploy services.

Instructions

GET /forwardAuth.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": "forwardAuth-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, idempotentHint and openWorldHint, so the safety profile is covered structurally. The description contributes nothing extra — no indication of what a 'provider' record contains, whether results are scoped to the caller, or whether configuration state affects the listing.

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 short but that brevity reflects under-specification rather than economy — a raw path fragment is not a sentence that explains anything. There is no front-loaded purpose statement, only an HTTP verb and route.

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 the tool is simple (no parameters, no output schema), the description leaves the agent without any statement of what is returned or how the result relates to the many sibling list-provider tools. It is not wrong, but it is too thin to support correct selection.

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 about parameters for the description to clarify. Baseline 4 applies for a no-parameter 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 only restates the endpoint as 'GET /forwardAuth.listProviders', which is a bare restatement of the tool name. It does not say in plain terms that it lists the authentication providers configured for forward-auth, nor how that differs from siblings like scim-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 whatsoever on when to call this tool, when not to, or which of the several sibling provider-listing tools it should be preferred over. The agent must infer usage 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