Skip to main content
Glama

Create site

site_create

Add a site to a wiki, its home: whoever can read that wiki may sign in to the site, and the wiki's admins and organization owners manage it. Requires an admin of the wiki or an organization owner. With no source it gets a code tree of its short name, made if the organization has none. Its short name must be free in the organization.

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

Input Schema

NameRequiredDescriptionDefault
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.
nameYesThe site's name; its short name and address come from it.
wikiYesThe name of the site's home wiki, e.g. general.
sourceNocode:<tree>, a code tree of the organization's. Leave it out for a tree of the site's short name.
capabilitiesNoWhat the site may do in its home wiki. ["read"] is read-only; ["read", "write"], the default, lets the site write pages and records there, within what each person signed in may do.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare the read/write/destructive/open-world profile; the description adds the access model (anyone who can read the wiki may sign in), the linkage of admins and owners to management, the uniqueness constraint on the short name, and the notable side effect that a code tree may be created implicitly. It omits what the call returns and whether repeating the call with the same name fails or is idempotent.

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 compact clauses, front-loaded with the action and the access consequence before the prerequisites and defaults. Some phrasing is dense and colon-chained ("a wiki, its home:"), but no sentence is filler.

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 5-parameter creation tool with full schema coverage and no output schema, the description covers permissions, defaults, implicit resource creation and naming constraints, which is most of what an agent needs. The remaining gap is the shape of the result and behavior on duplicate short names, though the latter is implied by the uniqueness rule.

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 the baseline is 3. The description adds only a little beyond the schema: it restates the source default (already in the source field's description) while clarifying that the derived tree is created if absent, and it contributes the short-name uniqueness rule for name that the schema itself does not state.

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?

"Add a site to a wiki, its home" gives an explicit verb (add/create) and resource (site) plus its scoping relationship to a wiki. It is distinguishable from wiki_create and code_create by naming the site resource and its home wiki, though it never explicitly contrasts itself with site_attach, which an agent might confuse it with for the same site/wiki pairing.

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?

It states the precondition plainly ("Requires an admin of the wiki or an organization owner") and describes the default path when source is omitted, which tells the agent this call can succeed without a source. It does not name alternatives such as site_attach or site_update, so the choice between creating a site and attaching an existing one is left to inference.

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