Skip to main content
Glama

Detach wiki from site

site_detach
Destructive

Stop a site using one of the organization's wikis. Requires an admin of the wiki, an organization owner, or an admin of the site's home wiki. A site's home can't be detached; move its home first. A published site picks up the change when it is next published.

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": {
      "id": "<id>",
      "wiki": "<wiki>",
      "org": "<org>"
    },
    "name": "site_detach"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe site's short name (its name lowercased, other characters made hyphens, e.g. deal-flow), or its client id.
orgYesslug of the organization whose trees and sites to use. Required on every call, even when only one organization is listed; a path never names it.
wikiYesThe wiki's name, e.g. general.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true. The description still adds real context beyond them: the authorization roles required, the home-wiki restriction, and that a published site only picks up the change on its next publish. It stops short of saying whether the wiki itself or its content survives detaching.

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

Conciseness5/5

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

Three sentences, each doing distinct work: the action, the permissions and restriction, and the propagation behavior. The action is front-loaded and there is no filler.

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

Completeness5/5

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

For a three-parameter mutation with full schema coverage, no output schema, and annotations covering the safety profile, the description supplies everything an agent needs: what it does, who may call it, the one blocking condition, and when the effect materializes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all three parameters are already documented in the schema. The description's mention of the 'site's home wiki' relates loosely to the wiki parameter but adds no format or syntax detail beyond what is already supplied.

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

Purpose5/5

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

States a specific verb and resource in the opening sentence: stop a site from using a wiki. That is the precise inverse of the sibling site_attach, so an agent can route between them without opening either schema.

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

Usage Guidelines4/5

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

Names the preconditions for use (wiki admin, organization owner, or admin of the site's home wiki) and an explicit blocking case: a site's home can't be detached, move its home first. It does not name an alternative tool for the attach case, but the when-can't guidance is concrete.

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