Skip to main content
Glama

Revoke wiki access

wiki_revoke
Destructive

Take away the grant one person or one team holds on a wiki. On a wiki open to the organization they keep what every member holds; on a restricted wiki they lose it, and its last grant cannot be revoked. 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>",
      "kind": "<kind>",
      "id": "<id>",
      "org": "<org>"
    },
    "name": "wiki_revoke"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe person's user id (members_list) or the team's id (team_list): user_2abc, team_9xyz. Never a name, a slug or an email.
orgYesslug of the organization whose wiki to use. Required on every call, even when only one organization is listed; a path never names it.
kindYesWhether the grant is to one person (user) or to a team.
wikiYesThe wiki's name, without a colon or a path (general).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the safety profile is covered; the description goes beyond them with real consequence detail — on an open wiki the principal keeps organization-wide access, on a restricted wiki they lose it, and the final grant is irrevocable. It also discloses that the action lands in the organization's audit log. Missing only idempotency and what a repeated revoke does.

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 short sentences, front-loaded with the action and then the consequences and prerequisites; nothing is filler. Slightly dense with clause stacking ('on a restricted wiki they lose it, and its last grant cannot be revoked'), but every sentence earns its place.

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 destructive, four-required-parameter tool with no output schema, the description supplies permissions, branching outcomes by wiki visibility, an edge case, and audit disclosure — enough for correct invocation. The main residual gap is return behavior, which is not covered anywhere.

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%, including id format constraints, the mandatory org slug, and the kind enum, so the baseline is 3. The description adds only the framing 'one person or one team,' which the kind enum and pattern already convey, and contributes no new guidance on the wiki or id parameters.

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?

Specific verb and resource: 'Take away the grant one person or one team holds on a wiki,' which precisely delimits the operation to an existing grant and to a single principal. It is clearly distinguishable from wiki_grant and wiki_remove in substance, though it never names the inverse tool explicitly.

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?

States the authorization prerequisite (admin of the wiki or organization owner) and one hard exclusion (the last grant on a restricted wiki cannot be revoked). It stops short of routing the agent between this and sibling tools such as wiki_grant or wiki_remove, so the when-to-use boundary is only implied.

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