Skip to main content
Glama
bim-ba

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Revoke Wiki page access

wiki_access_delete
Destructive

Revoke a specific access entry on a wiki page to immediately remove a user's grant. The page owner's own entry cannot be revoked.

Instructions

Revoke one access entry on a wiki page — the holder loses that grant at once.

The page owner's own entry cannot be revoked.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_idYesNumeric id of the page.
access_idYesId of the access entry, from the page's ``access_lists``.
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, idempotentHint=false, and readOnlyHint=false, so the safety profile is covered. The description still adds real value by stating the revocation is immediate and that the owner's entry is protected, both of which are behavioral facts not in the annotations.

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 short sentences, effect first, constraint second. Every clause earns its place and nothing is padding.

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 single-entry revocation with full annotation coverage and a well-documented schema, the description supplies the key behavioral facts an agent needs. The only gap is the absence of explicit routing to sibling access tools, which the annotations and schema cannot supply.

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 a thorough description of prevent_selflock and the access_lists source of access_id, so the schema carries the parameter burden. The description adds no syntax or format detail beyond that, which matches the baseline 3.

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 one access entry on a wiki page') and immediately clarifies the effect ('the holder loses that grant at once'). This clearly distinguishes it from sibling tools like wiki_access_create, wiki_access_update, and wiki_access_clear.

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?

Gives one useful usage constraint — the page owner's own entry cannot be revoked — which guides the caller. However, it never names or contrasts with the obvious alternatives (wiki_access_update for modifying a grant, wiki_access_clear for wiping all entries), so the when-to-use-this-vs-that guidance is only implied.

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