Skip to main content
Glama

Update organization security settings

update_org_security
DestructiveIdempotent

Change security settings of an organization. require_mfa makes every member pass two-step verification before they can open organization flows (the caller must have two-step verification on). allow_public_publish false blocks public links. transcript_retention_days deletes transcripts of organization flows after that many days (null turns it off). allow_external_collaborators false lets members share organization flows only with other members. allowed_domains limits invitations and sharing to those email domains (it must include your own domain; an empty list allows all). Only an owner or an admin can do this. join_mode and join_domains control who can join. idle_timeout_minutes signs idle members out. require_public_password makes public links need a password. Only an owner can loosen a rule.

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": {
      "org_id": "<org_id>"
    },
    "name": "update_org_security"
  }
}

Input Schema

NameRequiredDescriptionDefault
org_idYesOrganization id from list_organizations.
join_modeNoWho can join: invite only, anyone with an email at a join domain, or join domain after admin approval.
require_mfaNoRequire two-step verification for all members.
join_domainsNoCompany email domains for join_mode domain_open or domain_request. An owner or admin must have an email at each domain. Personal domains such as gmail.com are not allowed.
allowed_domainsNoEmail domains allowed for invitations and sharing, for example ["acme.com"]. Include your own domain. [] allows all domains. Up to 20.
scim_transfer_toNoEmail of a member who gets the flows of a member that SCIM removes. null means the first owner.
scim_default_roleNoRole for members that SCIM adds. Only an owner can pick admin.
allow_public_publishNoAllow public web links for organization flows.
idle_timeout_minutesNoSign members out after this many idle minutes: 15, 30, 60, 120, 240, or 480. null turns it off.
require_public_passwordNoRequire a password on public links of organization flows. Open public links stop working until the owner adds a password.
transcript_retention_daysNo1 to 3650 days, or null to keep transcripts.
allow_external_collaboratorsNoAllow sharing organization flows with people who are not members. Existing outside collaborators stay until remove_external_collaborators.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / idle_timeout_minutes
      Added value: +{
      +  "description": "Sign members out after this many idle minutes: 15, 30, 60, 120, 240, or 480. null turns it off.",
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / join_domains
      Added value: +{
      +  "description": "Company email domains for join_mode domain_open or domain_request. An owner or admin must have an email at each domain. Personal domains such as gmail.com are not allowed.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / join_mode
      Added value: +{
      +  "description": "Who can join: invite only, anyone with an email at a join domain, or join domain after admin approval.",
      +  "enum": [
      +    "invite",
      +    "domain_open",
      +    "domain_request"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / require_public_password
      Added value: +{
      +  "description": "Require a password on public links of organization flows. Open public links stop working until the owner adds a password.",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the destructiveHint=true / idempotentHint=true annotations, it discloses real side effects: transcripts are deleted after the retention window, open public links stop working when require_public_password is set, and existing external collaborators persist until remove_external_collaborators. It also flags the caller-side MFA requirement. It does not explain the SCIM parameters' behavior, which keeps this short of a 5.

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

Conciseness3/5

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

It is front-loaded and dense, but several clauses are pure schema echo ('join_mode and join_domains control who can join', 'idle_timeout_minutes signs idle members out', 'require_public_password makes public links need a password') and earn no place. The list of parameters reads as a walkthrough of the schema rather than prioritized guidance.

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 12-parameter destructive mutation with no output schema, the description covers permissions, destructive consequences, and most parameter edge cases. The SCIM transfer/default-role parameters are the notable gap, left to the schema alone.

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 100%, so the baseline is 3, but the description genuinely adds meaning for several parameters: allowed_domains must include your own domain and an empty list allows all, transcript_retention_days null turns it off, and require_mfa requires the caller to already have two-step verification. A few clauses (join_mode, idle_timeout_minutes, require_public_password) merely restate the 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?

Opens with a specific verb and resource ('Change security settings of an organization'), which clearly separates it from the read-only sibling get_org_security. It is clear, but the sibling differentiation is left implicit rather than named.

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?

The description establishes prerequisites ('Only an owner or an admin can do this') and an asymmetric rule ('Only an owner can loosen a rule'), which tells the agent when the call will succeed. It never explicitly says to read current settings with get_org_security first or when to prefer that tool, so the routing guidance is implied rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources