Skip to main content
Glama
bim-ba

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Update Wiki page access

wiki_access_update
Idempotent

Change the role or inheritance of a single wiki page access entry, excluding the owner's own entry. Update permissions or subpage reach for one user or group.

Instructions

Change the role or reach of one access entry on a wiki page.

The page owner's own entry cannot be changed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesThe new ``role`` and/or ``inheritance`` (one at least).
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

A3.6/5.0
Behavior3/5

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

Annotations already declare it non-read-only, idempotent, and non-destructive, so the safety profile is covered externally. The description adds one behavioral rule not present in the annotations (the owner's entry is immutable), but says nothing about partial-update behavior, reversibility, or authorization needs.

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, front-loaded with the core action and followed immediately by the key constraint. Zero filler; every sentence carries 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 mutation tool with full parameter documentation and annotations covering the safety profile, the description supplies the essential additional rule. It stops short of describing partial-update semantics or the response shape (no output schema exists), leaving a small gap.

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 coverage is 100%, so the schema already documents all four parameters in depth, including the nested body fields and prevent_selflock. The phrase 'role or reach' loosely maps to the body's role/inheritance fields but adds no format or semantics beyond the schema, so baseline 3 applies.

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?

Names a specific verb and resource ('Change the role or reach of one access entry on a wiki page') and scopes it to a single entry, which separates it from bulk operations like wiki_access_clear. It does not, however, explicitly contrast itself with wiki_access_create or wiki_access_delete, so the differentiation rests mostly on the name.

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?

Provides one exclusion ('the page owner's own entry cannot be changed') but no positive guidance on when to prefer this over wiki_access_create/delete, nor any prerequisites such as required permissions. Usage is implied by the update verb rather than stated.

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