Skip to main content
Glama
MCP Dokploy Online
by igoruam

sso-addTrustedOrigin

Idempotent

Adds an origin to the SSO trusted list so approved domains can authenticate through Dokploy SSO.

Instructions

POST /sso.addTrustedOrigin

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": {
      "origin": "<origin>"
    },
    "name": "sso-addTrustedOrigin"
  }
}

Input Schema

NameRequiredDescriptionDefault
originYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/5.0
Behavior2/5

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

Annotations already declare openWorldHint=true and idempotentHint=true, so the safety/mutation profile is partly covered. However, the description adds no behavioral context: it doesn't say what happens if the origin already exists (idempotency behavior), whether the origin must be a full URL or scheme+host, or whether the list has a size cap.

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 definition is extremely short, but conciseness must still be earned by conveying useful information — here it conveys nothing beyond the tool name. It is under-specified rather than efficiently front-loaded.

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?

This is a security-sensitive mutation tool with a format-sensitive string parameter and no output schema. The definition omits origin format expectations, duplicate handling, and error conditions, which leaves the agent likely to guess at invocation details.

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 parameter 'origin', so the description carries the burden and provides nothing. Critical semantics such as required format (scheme, host, port, wildcard support) or validation rules beyond minLength:1 are entirely absent.

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 "POST /sso.addTrustedOrigin", which restates the tool name in HTTP form rather than explaining what the tool does. An agent can infer a mutation on trusted SSO origins, but there is no verb+resource statement or differentiation from siblings like sso-updateTrustedOrigin or sso-removeTrustedOrigin.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/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 mention of prerequisites (e.g., SSO provider configured), and no exclusions or alternatives. The sibling names suggest overlapping operations, but the description gives the agent nothing to distinguish them by.

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