Vezlu
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| projectsA | List saved project names. |
| createB | Create a project with an empty main branch. Returns its head token. |
| branchesC | List a project's branch names and current head tokens. |
| branchB | Fork source into a new branch, guarded by the source's expected_head. |
| readC | Read all artifacts and head, or an immutable revision in this branch's ancestry. |
| writeA | Atomically replace whole text artifacts; null deletes. Requires the current expected_head. |
| historyC | List newest reachable revisions with ancestry and merge source references. |
| compareB | Show exact before/after text and unified differences between two branch heads. |
| mergeB | Combine selected artifact paths using common ancestry. Requires both current heads. Conflicts leave target unchanged. |
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 9 tools
Each tool maps to a distinct resource and action: project listing/creation, branch listing/forking, artifact reading/writing, revision history, head comparison, and merging. No two tools overlap in purpose, and guards like expected_head further clarify use.
Names are all lowercase and readable, but they mix resource nouns (projects, branches, history) with bare verbs (create, read, branch, write, compare, merge). The pattern is understandable but not a consistent verb_noun convention.
Nine tools is well-scoped for a lightweight versioned artifact store. Every tool covers a needed facet—projects, branches, revisions, reads/writes, diffs, and merges—without redundancy.
Core workflows for creating projects, branching, reading/writing artifacts, inspecting history, comparing heads, and merging are covered. Minor lifecycle gaps remain, such as deleting or renaming projects and branches, but agents can work around them.