Skip to main content
Glama
bim-ba

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Clear Wiki page accesses

wiki_access_clear
Destructive

Revoke all personal access grants on a wiki page except the owner's, so everyone else falls back to the page's access policy. The change cannot be undone.

Instructions

Revoke every personal access on a wiki page except the owner's.

Everyone but the owner falls back to the page's access policy. Irreversible: the revoked entries are not kept.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_idYesNumeric id of the page.
prevent_selflockNoRefuse the change if it would leave you without read access or the right to change accesses. Set it unless you mean to lock yourself out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.122.1
    • addedInput schema / properties / prevent_selflock / anyOf
      Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / prevent_selflock / default
      Previous value: -falseNew value: +null
    • removedInput schema / properties / prevent_selflock / type
      Removed value: -"boolean"
  2. First observedv0.67.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the owner is preserved, the resulting state is policy fallback, and the removal is irreversible because entries are not retained. It stops short of permissions/auth requirements, but for a destructive bulk-revoke that is a modest gap.

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 short sentences, zero filler, with the scope and the irreversibility warning front-loaded where a cautious agent will see them first.

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?

No output schema exists, so the description carries the burden of explaining the resulting access state, which it does. Combined with annotations and a fully documented two-parameter schema, an agent has nearly everything needed; only auth/permission prerequisites are absent.

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%, and the schema itself explains prevent_selflock in useful detail ('Refuse the change if it would leave you without read access...'). The description adds nothing about either parameter, which is acceptable but not additive, so the baseline 3 applies.

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 ('Revoke every personal access on a wiki page') plus a precise scope ('except the owner's'). This distinguishes it from the nearby single-entry siblings wiki_access_delete and wiki_access_update, which an agent can now tell apart without opening schemas.

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?

The description implies a bulk-clear use case and explains the resulting state ('everyone but the owner falls back to the page's access policy'), but it never states when to prefer this over wiki_access_delete or wiki_access_update, nor any prerequisites for invoking it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools