Skip to main content
Glama
MCP Dokploy Online
by igoruam

sso-getTrustedOrigins

Read-onlyIdempotent

Retrieve the trusted origins configured for SSO. Use it to verify which domains are allowed to initiate single sign-on authentication.

Instructions

GET /sso.getTrustedOrigins

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/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 and idempotency profile is covered by structured data. The description adds nothing beyond that — no indication of return shape, whether results are scoped to a provider, or whether an empty list is possible.

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 a single route string with no waste, but its brevity reflects under-specification rather than economy of expression. It reads like raw API metadata rather than a tool description.

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 output schema and a bare route as the entirety of the description, an agent gets almost no help beyond the annotations. For a zero-arg read tool this is survivable, but the definition does not explain what 'trusted origins' means or what the response contains.

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 forbids additional properties, so there is no parameter meaning for the description to explain. Baseline 4 applies; nothing is needed here.

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.getTrustedOrigins", which restates the tool name in endpoint form rather than describing what a trusted origin is or what the call returns. An agent can infer it reads SSO trusted origins from the name alone, but the description contributes no distinct verb+resource statement.

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 how this differs from sibling tools like sso-addTrustedOrigin or sso-removeTrustedOrigin, and no stated prerequisites (e.g. whether SSO must be configured). The agent is left to infer usage purely 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