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
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_project_boardA

Retrieves the living Tier 1 Project State Card (< 500 tokens). Call this tool at the beginning of a session or whenever you need situational awareness of the project. It synchronizes recent turns from local client transcripts (Antigravity and Codex) and compiles a high-density, deterministic markdown card. Contains:

  • 🎯 Project Goal & Scope

  • đź”’ Binding Invariants (lossless constraints, exact PRAGMAs, paths, versions)

  • 🏛️ Active Architectural Decisions (ADR IDs, titles, rationale, author, date)

  • đź“‹ Active Tasks & Handoff Baton (in-progress items with @owner, pending tasks)

  • ⚠️ Attention Required (health alerts: unowned tasks, unverified completions)

  • 🔄 Recent Ambient Activity (recent client messages, budget permitting) Args: target_tokens: Desired token budget ceiling for the briefing card (default: 450). Enforced accurately via the BPE tokenizer.

Returns: str: Clean Markdown-formatted Tier 1 State Card ready to be placed directly into your context window without prompt bloat.

record_decisionA

Records or updates an Architectural Decision Record (ADR) in Tier 2.

Call this tool whenever you establish a technical rule, make an architectural choice, or change an existing convention. Prevents decision drift and ensures subsequent agents (Claude, Codex, Antigravity) follow the agreed specification.

Lifecycle:

  • 'accepted': Active binding decision (automatically visible on Tier 1 State Card).

  • 'proposed': Under review or draft; not yet binding.

  • 'superseded': Replaced by a newer ADR; archived in Tier 2 history.

  • 'rejected': Proposed but explicitly abandoned with reason in rationale.

Formatting Rule: Preserve exact technical tokens in 'rationale' (e.g. file paths, PRAGMA flags, error codes, function signatures). Avoid fuzzy narrative paraphrasing.

Args: decision_id: Unique identifier string (e.g., 'ADR-001', 'ADR-STORAGE-WAL'). title: Short, descriptive title of the decision. rationale: Verbatim technical justification, constraints, and parameters. decided_by: Name or identity of the decider (e.g., 'claude', 'codex', 'human'). status: Decision status ('accepted', 'proposed', 'superseded', 'rejected').

Returns: str: Confirmation message with the recorded decision ID and status.

publish_contextA

Publishes or updates a key-value pair on the living project board.

Call this tool to record persistent high-level metadata that all agents need to see, such as project goals, active milestones, or shared environment variables.

Standard Keys:

  • 'goal': The primary objective of the repository/project.

  • 'current_milestone': The current phase or sprint objective (e.g., 'Phase 4: FastMCP').

  • 'constraints': Line-delimited or bulleted technical invariants.

Args: key: The configuration or metadata key (e.g., 'current_milestone', 'constraints'). value: The string value to store. If storing constraints, use newline-separated bullet points with exact technical parameters.

Returns: str: Confirmation message acknowledging the stored key-value pair.

update_taskA

Updates the status, owner, or validation notes of a task in the Tier 3 Task Graph.

Call this tool to claim work, hand off responsibility to another agent, or mark work as completed with proof of verification.

Status Conventions:

  • 'pending': Queued task waiting to be started.

  • 'in_progress': Currently being worked on. MUST have an 'assigned_to' owner to avoid triggering '⚠️ Attention Required' health warnings.

  • 'completed': Finished work. MUST include validation notes (e.g., test results, verification commands) for audit trail compliance.

Args: task_id: Unique task identifier (e.g., 'task-04', 'FEAT-BLACKBOARD'). status: Target status ('pending', 'in_progress', 'completed'). title: Optional updated title if creating or renaming the task. assigned_to: Agent or user claiming the baton (e.g., 'claude', 'antigravity', 'human'). notes: Progress updates or verification proof (e.g., '46/46 tests passed in 0.41s').

Returns: str: Confirmation message reflecting the updated task state.

get_recent_contextA

Retrieves recent conversation turns across all local AI clients.

Call this tool when you need ambient historical context from previous chat sessions without leaving the MCP workflow. Reads from the unified SQLite conversation ledger.

Args: limit: Maximum number of chronological turns to return (default: 10). source: Optional client filter: 'antigravity', 'codex', or None (for all clients).

Returns: list[dict[str, Any]]: Chronologically ordered list of turn dictionaries, each containing: - 'id': Deterministic turn ID (e.g., 'antigravity:caa4cbcc:447') - 'source': Originating client ('antigravity', 'codex') - 'session_id': Session or thread identifier - 'role': Message sender ('user', 'assistant') - 'content': Raw turn text - 'timestamp': ISO 8601 creation time

get_turnA

Retrieves a single uncompressed, un-summarized conversation turn by its exact ID (Tier 4).

This is the core of Project-M's Lossless Provenance Engine. When an ADR or task references a source anchor (e.g., 'turn:antigravity:caa4cbcc:447'), call this tool to retrieve the 100% complete, unedited historical message.

Guarantees:

  • Zero detail loss: Full terminal outputs, code snippets, and error tracebacks.

  • Zero hallucination: Exact raw payload as ingested from the local client transcript.

Args: turn_id: Deterministic turn identifier (e.g., 'antigravity:caa4cbcc:447' or 'codex:msg-982').

Returns: dict[str, Any]: Complete turn record with source, role, timestamp, and uncompressed content. str: Not-found message if the ID does not exist in the database.

get_project_summaryA

Retrieves a structured diagnostics and health summary of the project.

Call this tool for automated programmatic verification of repository state health. Returns exact counts and validation warnings without requiring Markdown parsing.

Returns: dict[str, Any]: Diagnostic record containing: - 'goal': Active project goal - 'current_milestone': Current milestone - 'total_decisions': Total recorded ADRs - 'in_progress_tasks': Count of active tasks - 'pending_tasks': Count of queued tasks - 'completed_tasks': Count of finished tasks - 'total_turns': Total recorded chat turns - 'is_healthy': True if zero unowned active tasks and zero unverified completions - 'warnings': List of active governance warnings - 'unowned_active_tasks': List of task IDs missing an assigned owner - 'unverified_completions': List of task IDs completed without notes

search_historical_contextA

Searches historical conversation turns across all local AI clients (Antigravity, Codex, and Claude Code) in sub-3ms using SQLite FTS5.

Call this tool when you need to recall past architectural debates, specific code examples, bash commands, or requirements from earlier sessions.

Args: query: Natural language or keyword search terms (e.g. 'decimal arithmetic', 'wal mode'). limit: Maximum number of matches to return (default: 5). role: Optional filter: 'user' (user requests) or 'assistant' (model outputs). source: Optional client filter: 'antigravity', 'codex', or 'claude_code'.

Returns: str: Formatted list of matches with full provenance citations (Client, Role, Timestamp, Turn ID, and content excerpt).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.1/5.0

Scored across 8 tools

Disambiguation4/5

Most tools target distinct resources (board, decisions, tasks, context turns). The main soft overlap is get_project_board vs get_project_summary, both returning project state (markdown card vs structured counts), and the three context tools (get_recent_context, get_turn, search_historical_context) which are clearly differentiated by mode (recent list, exact ID, keyword search). Descriptions help resolve these.

Naming Consistency5/5

All names are snake_case verb_noun (get_project_board, record_decision, publish_context, update_task, search_historical_context, etc.). Predictable verb-first pattern with distinct nouns, no mixed conventions.

Tool Count5/5

Eight tools is well-scoped for a project state/provenance server, mapping cleanly onto its tiers (board, ADRs, tasks, context, search). No redundant or filler tools.

Completeness4/5

Core lifecycle is covered: read board, record decisions, publish metadata, update tasks, retrieve and search context. Minor gaps remain—there is no dedicated tool to list or fetch an individual ADR (proposed/superseded ones are only reflected indirectly), and no explicit task-creation or deletion operations—but agents can work around these via the board card and summary.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues