Skip to main content
Glama
Sign In
Dexio

Dexio

by dexio-wiki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

set_visibility

Idempotent

Set or check who can open or edit a Dexio page, folder, or entire wiki using restricted, link-only, or published access.

Instructions

Who can open a page, a folder (everything under it) or the whole wiki (empty path), or change it. restricted: members, and people it was shared with by email. link: anyone with its url can read it; search engines are asked not to list it. published: public and listed on dexio.wiki, where anyone can find it and copy it, and search engines list it; a folder or the wiki only, with title and description for the listing. Without visibility it reports and changes nothing. A folder's or the wiki's wider setting still applies to what is in it. Opening something to the public is for when the person asks for it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "set_visibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
pathNo
titleNo
workspaceNoAnother workspace: its handle, or a link into it (list_workspaces lists them). Empty: this one.
visibilityNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (idempotent, non-destructive), the description discloses that link pages are de-listed from search engines, that published content is publicly listed on dexio.wiki and copyable, that omitting visibility makes the call report without changing anything, and that parent-folder/wiki settings still apply to children. That is substantive effect-level context. It stops short of stating who is authorized to make these changes or any error behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single paragraph is dense and mostly earns its place, but it opens by defining what visibility means instead of front-loading the action, and the inheritance sentence plus the closing 'for when the person asks for it' repeat context already implied. Structure is functional but not tight.

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?

With no output schema, the description usefully notes that a call without visibility reports current state without changing it, and it explains the semantics of each mode and inheritance. Missing pieces are authorization requirements and failure modes, which is a modest gap for a security-sensitive setting tool.

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 description coverage is only 17%, so the description must carry the load, and it does: it defines all three visibility enum values in detail, maps kind to page/folder/wiki, explains the empty-path case, and notes title/description are needed for a published listing. Only the workspace parameter is left unaddressed in the description text.

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 description conveys a specific resource and scope: visibility for a page, a folder (including everything under it), or the whole wiki when the path is empty, and 'or change it' implies the mutation. The verb itself is only implied rather than stated, and no sibling tool is named, so it falls short of the 5-level differentiation.

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?

It gives a conditional for the riskiest mode ('Opening something to the public is for when the person asks for it') and constrains 'published' to a folder or the wiki only, which is real usage guidance. However, it never contrasts this tool with alternatives such as change_pages or edit_page, nor states prerequisites, so guidance is implied rather than explicit.

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