Archipelago
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| completions | {} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| queryA | Read the map: every read is one call, query with the name of what to read and its params. With no name, every name with what it answers. actions says what one takes, whole: params read (a read or view, such as flat), action (or change, for its ops) or verb. An agent is given each answer without its empty fields and with long lists cut to what is read (params.full: true for all of it). The reads and their params: schema (type?, full?); search (q?, type?, status?, owner?, open?, include_archived?, limit?, full?); get (id, history?, full?); events (since?, target?, actor?, by?, before?, origin?, limit?, full?); proposals (status?, full?); picture (result?, look?); watch (after?, wait_seconds?); packs (none); acts (none); document (id, drawn?); publish_plan (within); published (id); share_figure (via, id); backup_download (none); places (canvas?); look (entity?, query?, lens?, style?, width?, height?, scheme?, fresh?, marks?); seeing (run?). Every other name is a view: flat, changed_since, spent, usage, notifications, sessions, saved_views, style, instructions, story, attention, graph, tree, hubs, brief. flat is the query: filter { find, only, not }, walk { over, steps }, limit. |
| changeA | The only way to change the map: a list of ops with a reason. A create’s ref lets later ops link to it, and a title or note in the same change names what it makes as {ref}. Give the source the facts came from. To add to a note or change a passage, send append or replace, not the whole body. An update with only the id says you checked the item and it is still true. Checked as a whole, then applied or held as a proposal for a human, by policy. A refused change is kept for a few minutes under a name the refusal gives: send retry and fixes (the ops that were wrong, by number), not all of it again. Closing a decision or hypothesis is held for the human, unless the workspace applies agents’ changes: then a decision must carry props.outcome and props.rationale, and is put to the owner later (attention, to_confirm). Each op is { op, ...its fields }: create (ref?, type, title, body?, status?, owner?, visibility?, confidence?, props?, source?); update (id, title?, body?, append?, replace?, status?, owner?, visibility?, confidence?, props?); link (type, from, to, props?, confidence?, source?); unlink (relation); archive (id); forget (id, reasons?); restore (id); merge (keep, drop); define_type (type). query actions with action change says each field. |
| undoA | Reverse one change set (its id is on every event it logged) by applying the opposite as a new change: created items are archived, edits put back, links removed or restored. An edit changed again since is left alone and reported. Subject to the same policy as any change. |
| captureC | Put something on the map: an item and its links, or a record of what happened. Call with the action and its params. Its actions: session_start (title?, task?, surface?, cwd?, remote?, session_id?, branch?, source?); picture_put (result, data, content_type); backup (none); import_audit (connection). query actions says what each does. |
| assignC | Give work to someone, inside the map or outside it: an owner, a person waited on, a party asked to act. Call with the action and its params. Its actions: claim (resource, holder, for?, reason). query actions says what each does. |
| reportC | Say that something happened or is so: progress, a result, a payment received, a check that it is still true. Also answers the owner with a view: show, with a kept view or an ad-hoc lens and style. Call with the action and its params. Its actions: session_update (run, status?, note?, task?, branch?, title?); session_end (run, outcome?, reason?, summary?, still_true?, cannot_tell?, cannot_tell_rest?); tell (run, said, about?, links?, replaces?, finding?); run_report (repo, title, ok?, tokens?, cost_usd?, turns?, link?, summary?, surface?); rechecked (repo, summary?); show (entity?, query?, lens?, style?, screen?, note?, look?, width?, height?, scheme?, pane?, run?); check_connections (none); health (heartbeat?, monitor?, msg?, live?, idle?, said?). query actions says what each does. |
| askC | Put a question to someone and wait for the answer. Call with the action and its params. Its actions: notify (title, body?, level?, about?); publish_ask (within, reason?). query actions says what each does. |
| settleC | Close a question by someone's word or by evidence: a decision made, a hypothesis borne out. Call with the action and its params. Its actions: confirmed (upto, basis). query actions says what each does. |
| reviseC | Change, correct or undo what is on the map. Call with the action and its params. Its actions: release (resource, holder?, reason); places_put (canvas?, moves?, clear?); publish (id, authority?); publish_all (within, authority?); undo (changeset). query actions says what each does. |
| drawA | Draw a view in this chat, for the person reading it, in a client that draws MCP Apps (Claude chat). Elsewhere nothing is drawn: report show opens it on their canvas, query look gives you the picture. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| view | Draws a view of the map in the chat that asked for it. |
TDQS
Scored across 10 tools
Several tools appear to do the same thing: change claims to be the only way to modify the map, while revise also says it can change/correct/undo the map, and undo duplicates revise's undo action. query, report show, and draw all overlap around reading/rendering views, while capture, change, and report overlap around recording events or map state. Agents will struggle to choose correctly without trial and error.
All tool names are lowercase single imperative verbs, so the naming style is consistent and readable. The main weakness is that several are broad meta-verbs (query, change, revise) rather than predictable verb_noun names, making their semantics less obvious despite consistent formatting.
Ten top-level tools is a reasonable count on the surface, but each tool is actually a mega-dispatcher bundling many actions, so the effective tool surface is much larger and poorly scoped. The count hides substantial complexity rather than reflecting a clean, well-bounded set.
The surface broadly covers the apparent domain: reading/searching the map, creating/updating/linking/archiving/restoring items, sessions, reporting, publishing, proposals, backups, and drawing. Some lifecycle edges are unclear or buried in dispatcher actions, but there are no obvious severe gaps for the stated scope.