dibs
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": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| dibs_checkA | Check whether files are claimed by another agent. FREE means safe to edit; HELD tells you who has them and until when. |
| dibs_claimA | Claim files or glob patterns before editing them, so parallel agents don't collide. Returns GRANTED with an expiry, or DENIED with who holds the files, why, and until when. Re-claiming the same patterns renews your lease. |
| dibs_lesson_addA | Save a lesson for future agents as a markdown file under .dibs/lessons/ (committed with the repo, shared via git). Record gotchas, conventions, and hard-won fixes — not routine work logs. |
| dibs_lesson_searchA | Search lessons recorded by previous agents before working in unfamiliar territory. Returns ranked matches with snippets. |
| dibs_noteA | Broadcast a short note to every agent working on this repo. Use it for handoffs and heads-ups that affect others. |
| dibs_notesA | Read notes from other agents (marks them read). Check at the start of a session and before starting new work. |
| dibs_releaseA | Release your claims when you finish working on an area, so other agents can proceed. Leases also expire on their own. |
| dibs_statusA | See the whole picture: active agents on this repo, every live claim with expiry, and your unread note count. Call this at the start of a session. |
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 8 tools
Each tool addresses a distinct coordination task—claim management, status overview, lessons, and notes—with no overlap. An agent can easily tell which tool to use for claiming, checking, releasing, or communicating.
All tools share the 'dibs_' prefix and use snake_case, but 'dibs_status' and 'dibs_notes' are nouns while most others are verbs (release, check, claim, etc.). This minor inconsistency is easy to overlook given the clear prefix and short names.
With 8 tools, the server is well-scoped for its purpose: 4 for claim/status management, 2 for lessons, and 2 for notes. Each tool earns its place without redundancy or bloat.
The tool surface fully covers the coordination domain: claim, release, check, status, lesson add/search, and note broadcast/read. There are no obvious missing operations—manual expiry is unnecessary because leases auto-expire, and release complements claim.