Skip to main content
Glama

Attach wiki to site

site_attach

Let a site work in one of the organization's wikis as the person signed in to it: read, and write pages and records where that person may. Pass capabilities ["read"] to attach it read-only; attaching again changes it. Requires an admin of the wiki or an organization owner. 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_attach"
  }
}

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.
capabilitiesNo["read"] attaches the wiki 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 already declare this is a non-destructive, non-open-world mutation, and the description adds materially: the authorization prerequisite, the idempotent/update semantics of re-attaching, and the deferred propagation rule that a published site only picks up the change on next publish. Return shape and failure modes are not described, but the important side effects are.

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?

Front-loaded with the capability statement, then permissions, then propagation timing, in three tight sentences. The lead phrase 'read, and write pages and records where that person may' is slightly redundant with the capabilities parameter but not wasteful.

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 four-parameter mutation with no output schema, the description covers the essentials: permission gate, capability semantics, idempotency, and when the change takes effect. Only error behavior and how to undo the attachment (via the detach sibling) are left implicit.

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 each parameter is already documented in the schema, including the capabilities enum and defaults. The description reinforces that access is bounded by what the signed-in person may do, but adds little syntax or format meaning beyond the structured fields.

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?

The description names a specific action (attach a site to a wiki) and both resources, and clarifies that re-attaching mutates the existing link rather than creating a second one. It does not explicitly point at site_detach as the inverse, but an agent can still distinguish the operation from siblings.

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 gives concrete usage conditions: pass capabilities ["read"] for read-only attachment, default is read+write, re-invoking changes the existing attachment, and the caller must be a wiki admin or organization owner. No explicit when-not-to-use guidance or named alternative (e.g. detaching) is provided.

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