Skip to main content
Glama
MCP Dokploy Online
by igoruam

sso-removeTrustedOrigin

Destructive

Removes a specified trusted origin from SSO configuration, preventing unauthorized authentication redirects from that origin.

Instructions

POST /sso.removeTrustedOrigin

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

Input Schema

NameRequiredDescriptionDefault
originYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is covered externally. The description adds nothing beyond that: no statement about irreversibility, what happens to sign-in behavior for the removed origin, required permissions, or error behavior for unknown origins.

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, but terse to the point of under-specification rather than efficient. The single token of content duplicates the tool name and provides 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?

For a destructive, open-world mutation with one undocumented parameter and no output schema, the description supplies essentially none of the context an agent needs. Nothing explains consequences, confirmations, or return behavior.

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 'origin' parameter, so the description carries the burden. It says nothing about the expected format (full URL vs scheme/host), case sensitivity, or what a valid identifier looks like, leaving the agent to guess beyond type: string, minLength 1.

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 'POST /sso.removeTrustedOrigin'. It conveys the verb (remove) and the resource (trusted SSO origin) encoded in the name, but adds no plain-language statement of what removing a trusted origin means or how it differs from siblings like sso-updateTrustedOrigin.

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 prerequisites, and no mention of alternatives such as sso-addTrustedOrigin or sso-getTrustedOrigins. The agent must infer usage entirely from the name and the sibling list.

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