Skip to main content
Glama
MCP Dokploy Online
by igoruam

sso-updateTrustedOrigin

Idempotent

Replaces an existing SSO trusted origin with a new origin, keeping authentication redirects and requests allowed from the correct domain.

Instructions

POST /sso.updateTrustedOrigin

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": {
      "oldOrigin": "<oldOrigin>",
      "newOrigin": "<newOrigin>"
    },
    "name": "sso-updateTrustedOrigin"
  }
}

Input Schema

NameRequiredDescriptionDefault
newOriginYes
oldOriginYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations already declare openWorldHint=true and idempotentHint=true, but the description adds nothing beyond them: it does not say whether the old origin must exist, what happens if it is absent, whether auth/admin privileges are required, or what the response contains. For a mutation endpoint the description carries no behavioral disclosure at all.

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 single line is short but short due to under-specification rather than economy; it conveys a route, not usable meaning, and offers no front-loaded statement of intent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A two-required-parameter SSO mutation tool with no output schema and no documented parameters requires the description to explain the rename semantics and constraints; it supplies none of that.

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

Parameters1/5

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

Schema description coverage is 0% for two required string parameters, so the description must compensate and does not. It never explains that oldOrigin must exactly match an existing entry or what format newOrigin should take (scheme, host, port, path).

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.updateTrustedOrigin", which restates the tool name and HTTP route without stating in plain language what the operation does (presumably replace one trusted SSO origin with another). It technically distinguishes the tool from siblings like sso-addTrustedOrigin or sso-removeTrustedOrigin only via the name itself, not the description.

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 versus sso-addTrustedOrigin, sso-removeTrustedOrigin, or sso-getTrustedOrigins, and no mention of prerequisites such as the old origin already existing in the list. An agent must infer everything 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