Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_pagesA

List the wiki's pages, or one folder's, with title, a one-line description (frontmatter description: if set, else the first sentence), word count and last change, in path order, 200 at a time. When more remain it gives next_offset and the subfolders with their page counts. Uploaded files are in list_files.

list_filesB

List the wiki's uploaded files, or one folder's, with size, type and last change.

list_workspacesA

The workspaces this key can reach, acting as its person: this one, the others they are a member of (read and write), and those that share pages with them (read-only, with what each shares). Pass one's handle as workspace to any tool to act there.

wiki_healthB

Check the wiki: broken links (the only problems), and as information: missing pages most linked to (wanted), pages that may be stale (past their stale_after date, or unchanged stale_days while pages they link to changed), pages named without a link (unlinked_mentions), pages over long_page_words, the most linked pages, and pages with no links.

read_pageA

Read a page: a JSON header (version, to pass back as base_version; links in and out; broken links), then the markdown as plain text. Read part of a long page with outline=true (headings and line numbers), section (one heading's section), or offset and limit (lines). One read returns at most 128 KB; next_offset continues. revision reads a past version from page_history. On an uploaded file's path it returns the image, or a document's text.

search_pagesA

Search the wiki's paths, titles and text. Matches every word (common words dropped, substrings count), best first; "quoted text" matches exactly; regex=true takes a Python regular expression. Returns pages with matching lines and line numbers. Search before answering about the workspace and before creating a page.

page_historyA

A page's revisions, newest first, or without path the wiki's latest changes: when, op, agent, person (the account behind it), author (API key or app), note, version. agent filters to one agent. Works for deleted pages.

write_pageA

Create a page or replace its whole text. If a page on the topic exists, use edit_page. base_version makes the write fail if the page changed since you read it.

edit_pageA

Change part of a page. old_text replaces an exact string, which must be unique unless replace_all. section alone replaces that whole section, heading included; with old_text, old_text need only be unique within it. Empty new_text deletes.

append_pageA

Add text to the end of a page on a new line, creating the page if needed. For logs and running lists.

delete_pageA

Delete a page. Its history is kept, and the result says how to restore it. Returns the pages whose links to it are now broken.

move_pageA

Rename or move a page, rewriting the links to it (unless update_links is false). Fails if new_path exists.

upload_fileA

Get a one-time URL for uploading a file (image, PDF, deck, anything up to 100 MB) to path, e.g. raw/deck.pdf, then PUT the file to it from a shell: curl -T FILE URL. It works once, for 15 minutes, and replaces a file at path. Pages link to files by path.

delete_fileB

Delete an uploaded file. Permanent: files keep no history.

change_pagesA

Apply up to 200 changes as one step, all or none: write, edit, append, delete and move, each with its one-page tool's fields, run in order. dry_run reports what would change and which links would break, writing nothing.

set_visibilityA

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.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 16 tools

Disambiguation4/5

Most tools target a distinct resource+action: page CRUD (read/write/edit/append/delete/move), file ops, search, history, health, visibility. The main overlap is write_page vs edit_page vs append_page, which the descriptions clarify (whole replace, partial, end-append), and change_pages explicitly reframes those same operations as a batch, so boundaries are mostly clear but require reading.

Naming Consistency4/5

Almost all names follow a consistent snake_case verb_noun pattern (list_pages, read_page, write_page, edit_page, delete_page, move_page, upload_file, set_visibility). Minor deviations are the noun-only names wiki_health and page_history, which still fit the vocabulary and remain readable.

Tool Count4/5

16 tools is slightly above the ideal band but well-scoped for a full wiki: page lifecycle, file handling, search, history, health, batch changes, and visibility each earn their place. No redundant or trivial tools inflate the count.

Completeness4/5

Strong lifecycle coverage: read/write/edit/append/delete/move pages, upload/delete/list files, search, revision history, health checks, batch changes, and visibility control. Minor gaps exist (no explicit page-restore or file rename/move tool, and file read is folded into read_page), but core workflows have no dead ends.

Maintenance

ActivityMaintained
ResponsivenessNo issues