Skip to main content
Glama
Sign In
Cloady

Cloady

Official
by Cloady
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Set Workspace Sso

setWorkspaceSso
Destructive

Connect an OpenID Connect identity provider to a workspace for single sign-on; verify domain TXT ownership before saving so connections are live. Emails at the domain join as developers.

Instructions

Connect an OpenID Connect identity provider for single sign-on. Refuses a domain whose _cloady.<domain> TXT record doesn't carry the workspace's txtValue yet, so a saved connection is always live. Anyone the provider signs in with an email at the domain joins the workspace as a developer. Omit clientSecret to keep the stored one. Requires admin.

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": {
      "workspaceSlug": "<workspaceSlug>"
    },
    "name": "setWorkspaceSso"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestBodyNoThe JSON request body.
workspaceSlugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.18.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only say destructive and open-world; the description adds the pre-flight gate (refuses unverified `_cloady.<domain>` TXT record), the admin requirement, and the consequential side effect that anyone signed in at that domain joins as a developer. It does not say what happens to an already-connected provider when this is called again, which matters for the destructiveHint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four dense sentences, front-loaded with the action, with no filler. Minor ambiguity in 'the workspace's txtValue', which an agent must infer comes from getWorkspaceSso.

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

Completeness4/5

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

For a nested-body mutation with no output schema and no annotations beyond safety hints, it covers prerequisites, auth, secret handling, and the membership side effect. Missing only replace-vs-error behavior on reconnect and any indication of the response.

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?

Schema coverage is 50% and the nested requestBody properties carry no descriptions, so the description does heavy lifting: it explains the domain must be TXT-verified and that omitting clientSecret preserves the stored secret. issuer and clientId receive no added meaning, and 'the workspace's txtValue' references a value not present in this schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Connect an OpenID Connect identity provider for single sign-on'), which is clearly distinguishable from getWorkspaceSso and deleteWorkspaceSso. It never names those siblings, so the differentiation is implicit rather than explicit.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives real prerequisites ('Requires admin', DNS TXT verification must already be in place) and an implied update path ('Omit clientSecret to keep the stored one'), but never says when to call this versus getWorkspaceSso to inspect or deleteWorkspaceSso to tear down.

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