Skip to main content
Glama
MCP Dokploy Online
by igoruam

sso-register

Idempotent

Registers an SSO identity provider by submitting provider ID, issuer, and allowed domains, with optional OIDC or SAML configuration for authentication.

Instructions

POST /sso.register

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": {
      "providerId": "<providerId>",
      "issuer": "<issuer>",
      "domains": "<domains>"
    },
    "name": "sso-register"
  }
}

Input Schema

NameRequiredDescriptionDefault
issuerYes
domainsYes
oidcConfigNo
providerIdYes
samlConfigNo
organizationIdNo
overrideUserInfoNo

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?

With annotations providing only openWorldHint and idempotentHint, the description carries the full behavioral burden and supplies none of it. It does not disclose that this operation handles sensitive material (clientSecret, privateKey, cert), whether re-registering an existing providerId overwrites it, what side effects occur (callback URLs registered with an IdP), or what a successful response contains. The HTTP verb is the only behavioral hint offered.

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 technically terse, but this is under-specification rather than conciseness — the text carries no usable content beyond the method and path. There is nothing to trim and nothing that earns its place as guidance.

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?

This is a high-complexity write tool with nested polymorphic configuration objects, required secrets, no schema descriptions, and no output schema. A one-line route string is wholly inadequate: an agent cannot determine required nested fields, config-type selection, or the effect of a successful call from this definition.

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% across 7 parameters, including deeply nested oidcConfig, samlConfig, spMetadata and idpMetadata objects, and the description adds zero clarifying text. Nothing explains the relationship between providerId, issuer and domains, or when to supply oidcConfig versus samlConfig, leaving the agent to reverse-engineer required nested fields from an unannotated schema.

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 'POST /sso.register', which restates the tool name (sso-register) in transport terms rather than stating the operation. An agent can infer a create/registration action from the route and sibling names like sso-deleteProvider and sso-update, but nothing in the text says what an 'SSO registration' produces or which resource it creates.

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 mention of prerequisites (existing organization, provider ID uniqueness), and no routing to alternatives such as sso-update or sso-addTrustedOrigin. The agent receives no signal about when this call is appropriate versus the other sso-* siblings.

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