Skip to main content
Glama
MCP Dokploy Online
by igoruam

sso-showSignInWithSSO

Read-onlyIdempotent

Displays single sign-on sign-in options so Dokploy users can authenticate through their configured SSO provider.

Instructions

GET /sso.showSignInWithSSO

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-showSignInWithSSO"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.2/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, so the safety profile is covered. The description adds nothing beyond that — no indication that a sign-in flow may involve an external identity provider redirect or that auth state may be created despite the readOnly hint's framing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Six words with no filler, but the brevity comes from omission rather than discipline. It is technically concise and front-loaded, yet the single line carries no usable information.

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?

With no parameters and no output schema, the description is the only channel for explaining behavior, and it leaves the agent unable to know what a successful call produces or how to continue the flow. For an SSO sign-in entry point, that is a substantive gap.

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, so there is nothing for the description to disambiguate. Baseline 4 applies; the empty schema is self-explanatory.

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 'GET /sso.showSignInWithSSO', which restates the tool name rather than explaining what the tool does. An agent can infer this relates to beginning an SSO sign-in, but nothing states whether it returns a redirect URL, a SAML request, or provider metadata.

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 routing among the many SSO siblings (sso-one, sso-register, sso-listProviders, sso-enforceSSO). The agent must guess whether this is the entry point for login or an auxiliary lookup.

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