Skip to main content
Glama

Set wiki visibility

wiki_update
Destructive

Change who sees a wiki: org opens it to everyone in the organization (every member writes); restricted closes it to all but those granted it, and needs at least one grant first. Requires an admin of the wiki or an organization owner. Recorded in the organization's audit log.

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>",
      "visibility": "<visibility>",
      "org": "<org>"
    },
    "name": "wiki_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgYesslug of the organization whose wiki to use. Required on every call, even when only one organization is listed; a path never names it.
wikiYesThe wiki's name, without a colon or a path (general).
visibilityYesorg: everyone in the organization. restricted: only those granted it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, and the description earns credit for the extra context: authorization requirements (wiki admin or org owner), the precondition of at least one existing grant, and audit-log recording. It stops short of saying whether existing grants survive a switch to 'org' or what the response confirms, which matters for a destructive mutation.

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?

Two dense sentences: the action and its two modes come first, then the preconditions and audit note. No filler, no restatement of the title, and every clause carries operational information.

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 3-parameter, fully documented mutation with no output schema, the definition covers the action, mode semantics, prerequisites, and authorization. The one gap is post-call state: whether prior grants are preserved or dropped when switching to 'org', which the agent cannot derive from the schema or annotations.

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 baseline is 3, but the description adds meaning the schema does not: 'every member writes' clarifies the write implication of 'org' beyond the schema's 'everyone in the organization', and 'needs at least one grant first' is a precondition on the 'restricted' value that the schema omits.

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 opening clause 'Change who sees a wiki' names a specific verb and resource, and the two enum modes are spelled out with their effects ('org opens it to everyone', 'restricted closes it to all but those granted it'). It never names the related siblings (e.g. wiki_grant, access_wiki) it might be confused with, so differentiation is by implication only.

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?

Strong within-tool guidance: each visibility value is paired with the condition that selects it, and the prerequisite 'needs at least one grant first' tells the agent when a restricted call will fail. It gives no cross-tool routing (no 'to grant access use wiki_grant instead'), so the alternative-selection half is missing.

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