Waymark
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HUB_TOOLS | No | Set to 'full' to include the admin surface tools, default is 'core'. | core |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| memory_writeC | Create or replace a named memory node (project-scoped, or global if no project_id). |
| memory_readA | Read a single memory node by id or by project+name. |
| memory_searchA | Full-text search across all memory nodes. Use to find anything known about a topic. |
| task_createC | Create a handoff task for another agent or client. |
| task_listC | List tasks by status, project, assignee, or blocker. |
| task_updateB | Update task status, progress, blocker, or notes. |
| task_claimB | Atomically claim a pending task after validating assignment, capabilities, and dependencies. |
| session_logA | Record a session summary at the end of significant agent work. On outcome "partial"/"blocked" (or when next_steps are given) the hub automatically writes a handoff memory so the next agent resumes without retelling; outcome "completed" retires that auto-handoff. |
| context_getC | Build task-specific project context using deterministic ranking within a token budget. |
| workspace_resumeC | Restore compact project state for a new agent session in one token-budgeted call. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool has a clearly distinct purpose: context building, memory operations, session logging, task management, and workspace resumption. No overlapping functionality.
All tools follow a consistent verb_noun snake_case pattern (e.g., `memory_read`, `task_create`), making naming predictable and intuitive.
10 tools is well-scoped for the server's domain of agent orchestration and memory management, covering core operations without bloat.
Covers CRUD for memory (read, search, write) and tasks (create, list, update, claim) plus session logging and context. Minor gap: no explicit task deletion or memory deletion, but these are not critical for the intended workflows.