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
{}
prompts
{}
resources
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
project_agent_contextA

Build a compact context bundle around a card from direct relations, active conventions, open incidents and active project context. Prefer this over reading records one by one before working on a card.

project_card_archiveA

Move a closed card to the canonical archive directory. Only done and discarded cards can be archived; the ID and the file survive, so project_card_reopen undoes this.

project_card_claimA

Claim a card for an actor, move it to doing and optionally declare the filesystem scope that will be changed. Claim before editing anything the card covers; another actor's claim is refused unless forced.

project_card_createA

Create one canonical Work card with a concurrency-safe stable ID. Search first: this mints a new record rather than finding an existing one.

project_card_listA

List cards filtered by status, area, type, priority, parent or claim. Use before starting work; use project_search for full-text.

project_card_noteA

Append one timestamped line under a heading. Cheaper than rewriting the body and safe when two agents write at once.

project_card_patchA

Patch allowed card metadata using optimistic concurrency. Use expectedRevision whenever the card was read earlier. Declared axes go in changes.axes as { name: value }; an empty value clears one.

project_card_releaseA

Release your claim on a card and move it out of doing. Call when work stops, finished or not.

project_card_reopenA

Move an archived card back out of the archive directory and into a live status. The ID never changes, so every existing reference to it keeps resolving.

project_card_transitionA

Move a card to another protocol status. Moving to doing claims the card for the actor; review means the implementation is finished but unverified, and done requires evidence it ran, not a commit.

project_card_writeA

Replace the Markdown body of a card under the protocol's lock and revision check. Use project_card_note to append instead.

project_changelog_addA

Create an atomic unreleased changelog fragment and relate it to cards, decisions or other records. One fragment per user-visible change, written when the change lands rather than when the release is cut.

project_changelog_listA

List unreleased change fragments and cut releases, filtered by type, area or visibility.

project_changelog_patchA

Patch an unreleased changelog fragment using optimistic concurrency. Only works before a release consumes the fragment; afterwards the text belongs to that release.

project_changelog_previewA

Render selected unreleased fragments without mutating the repository. Use to read a release before project_changelog_release makes it permanent.

project_changelog_releaseA

Consume selected unreleased fragments and create a canonical release record. This moves fragment files into the release directory, so preview first: the fragments stop being separately editable.

project_doc_createA

Create a managed Markdown document with a stable DOC ID. Without an explicit folder the workspace docs.layout decides where it is written.

project_doc_listA

List indexed and managed documents, filtered by kind, status or freshness.

project_doc_moveA

Move a managed document to another folder below the managed docs root. The DOC ID never changes; use an empty folder for the root.

project_doc_patchA

Patch a managed document using optimistic concurrency. Indexed repository docs are intentionally read-only through this tool — edit those files directly.

project_doctorA

Validate Work, Docs, History, Memory, agent instructions, CI templates and cross-record references. Run before declaring work finished.

project_get_recordA

Read one canonical project record by stable ID, including body, revision, outgoing references, backlinks and health signals. The revision it returns is what a later write passes as expectedRevision.

project_memory_addA

Create a typed learning, decision, incident, convention or temporary context record. For knowledge that should change future behaviour — not for narrating what happened this session.

project_memory_graduateA

Mark a learning as graduated and link it to the convention, decision or documentation that now carries the durable rule. Create the target record first — graduating points at something that must already exist.

project_memory_listA

List learnings, decisions, incidents, conventions and context, filtered by collection or lifecycle status.

project_memory_patchA

Patch a durable memory record using optimistic concurrency. To retire one in favour of another use project_memory_supersede, which updates both sides.

project_memory_supersedeA

Supersede one memory record with another and update both sides atomically. Create the replacement first; neither record is deleted, so the superseded one stays readable and its ID keeps resolving.

project_nextA

Rank actionable cards: unblocked, unclaimed or claimed by you, highest priority first. Answers "what should I do now".

project_searchA

Search cards, documentation, changelog entries, releases and durable memory. Uses deterministic lexical ranking and an injected semantic provider when available.

project_workspaceA

Return the effective Workfile workspace, schema, enabled modules and mutation mode. Read this first when a vocabulary is project-declared: it reports the areas, axes, document kinds, changelog types and memory collections this project accepts.

Prompts

Interactive templates invoked by user choice

NameDescription
finish-workPrepare verification, documentation, changelog and status-transition checks before ending a task.
record-knowledgeChoose the correct memory collection and create a well-linked durable record.
start-workPrepare a safe execution prompt with bounded project context and claim instructions.

Resources

Contextual data attached and managed by the client

NameDescription
workspaceEffective Workfile workspace and schema.
healthCurrent Workfile doctor report.
protocolInstructions shared by humans and software agents.
ADR-0001memory · decisions · superseded
ADR-0002memory · decisions · accepted
ADR-0003memory · decisions · accepted
ADR-0004memory · decisions · superseded
ADR-0005memory · decisions · accepted
ADR-0006memory · decisions · accepted
ADR-0007memory · decisions · accepted
ADR-0008memory · decisions · accepted
ADR-0009memory · decisions · accepted
CHG-0001change · fixed · core
CHG-0002change · fixed · core
CHG-0003change · changed · docs
CHG-0004change · fixed · ui
CHG-0005change · added · search
CHG-0006change · added · core
CHG-0007change · added · search
CHG-0008change · changed · infra
CHG-0009change · security · infra
CHG-0010change · fixed · core
CHG-0011change · fixed · core
CHG-0012change · fixed · docs
CHG-0013change · fixed · core
CHG-0014change · added · core
CHG-0015change · changed · infra
CHG-0016change · changed · infra
CHG-0017change · fixed · core
CHG-0018change · fixed · docs
CHG-0019change · changed · ui
CHG-0020change · changed · ui
CHG-0021change · added · search
CHG-0022change · added · ui
CHG-0023change · added · ui
CHG-0024change · changed · ui
CHG-0025change · added · ui
CHG-0026change · fixed · docs
CHG-0027change · fixed · core
CHG-0028change · fixed · core
CHG-0029change · changed · core
CHG-0030change · changed · docs
CHG-0031change · added · core
CHG-0032change · added · core
CHG-0033change · changed · docs
CHG-0034change · added · core
CHG-0035change · fixed · core
CHG-0036change · changed · ui
CHG-0037change · changed · ui
CHG-0038change · fixed · ui
CHG-0039change · changed · ui
CHG-0040change · fixed · ui
CHG-0041change · fixed · ui
CHG-0042change · added · core
CHG-0043change · added · docs
CHG-0044change · internal · docs
CHG-0045change · fixed · core
CHG-0046change · fixed · core
CHG-0047change · added · infra
CHG-0048change · added · core
CHG-0049change · fixed · core
CHG-0050change · fixed · core
CHG-0051change · fixed · core
CHG-0052change · fixed · core
CHG-0053change · fixed · core
CHG-0054change · fixed · core
CHG-0055change · fixed · core
CHG-0056change · fixed · docs
CHG-0057change · fixed · docs
CHG-0058change · fixed · core
CHG-0059change · fixed · docs
CHG-0060change · fixed · core
CHG-0061change · fixed · ui
CHG-0062change · fixed · core
CHG-0063change · added · core
CHG-0064change · added · core
CHG-0065change · fixed · core
CHG-0066change · added · core
CHG-0067change · added · core
CHG-0068change · changed · docs
CHG-0069change · fixed · core
CHG-0070change · removed · infra
CHG-0071change · fixed · core
CHG-0072change · added · infra
CHG-0073change · fixed · mcp
CHG-0074change · fixed · core
CHG-0075change · fixed · core
CHG-0076change · fixed · ui
CHG-0077change · changed · ui
CHG-0078change · fixed · ui
CHG-0079change · changed · ui
CHG-0080change · added · ui
CHG-0081change · changed · ui
CHG-0082change · added · ui
CHG-0083change · fixed · ui
CHG-0084change · changed · ui
CHG-0085change · added · ui
CHG-0086change · fixed · core
CHG-0087change · changed · ui
CHG-0088change · fixed · mcp

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/illodev/workfile'

If you have feedback or need assistance with the MCP directory API, please join our Discord server