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
lognexus_statusA

Inspect the current Git branch, whether the directory is a Git repository, the active issue, the routing mode and the recommended model tier. Use when you need a cheap read-only snapshot before choosing a branch, a tier, or a next action. Not for reading the subtask contract (use lognexus_state_get) or for refreshing the state from Git and GitHub (use lognexus_state_sync).

lognexus_state_getA

Return the persistent LogNexus agent state (.lognexus/state.json) as stored on disk: active issue, current subtask and its file contract, completed subtasks and last synchronization timestamp. Use when you need the current contract or completion list and nothing has changed the branch since the last sync. Not for validating the state against the Git branch or GitHub (use lognexus_state_sync), and not for starting or finishing subtasks (use lognexus_state_set_task or lognexus_state_finish_task).

lognexus_state_syncA

Reconcile the persistent state with the current Git branch and GitHub metadata, rewriting .lognexus/state.json and returning the updated state. Use when you just checked out a branch, rebased, opened a PR, or suspect the stored state is stale. Not for a plain read of what is already on disk (use lognexus_state_get); sync mutates the store and runs git and gh.

lognexus_state_set_taskA

Mark a subtask as in progress and persist its closed delegation contract (allowed files, forbidden files, decision budget, verification command) plus the active issue tier. Equivalent to 'lognexus state set-task [title]'. Use when you begin a new subtask and need the file scope enforced by the commit engine and the audit. Not for marking a subtask complete (use lognexus_state_finish_task) and not for reading the contract (use lognexus_state_get).

lognexus_state_finish_taskA

Mark a subtask as completed in the persistent state and return the updated state. Equivalent to 'lognexus state finish-task '. Use when the subtask work has already been committed and its Git Note attached. Not for creating the commit itself (use lognexus_commit with finishTask: true, which finishes the task atomically) and not for editing the contract (use lognexus_state_set_task).

lognexus_state_clearA

Reset the persistent LogNexus agent state to empty. Equivalent to 'lognexus state clear'. Use when abandoning an issue, switching to an unrelated task, or recovering from a corrupted state file. Not for finishing a single subtask (use lognexus_state_finish_task); clearing is destructive and drops the whole contract.

lognexus_commitA

Atomically create a Git commit with conventional commit format, authorship trailers, subtask file contract validation, optional task finishing, and Git Note attachment in a single operation. Use when creating any commit on a LogNexus branch, including the atomic subtask commits that close a Tn. Not for retro-attaching a note to a commit that already exists (use lognexus_note_attach), and not for bypassing the gate: the commit engine refuses to run on a protected branch and rejects files outside the contract.

lognexus_note_showA

Read the LogNexus Git Note (refs/notes/lognexus) attached to a commit and return its parsed JSON payload. Defaults to HEAD. Use when verifying that a commit carries the expected tier, subtask and contract before a review or a merge. Not for creating or repairing notes (use lognexus_note_attach).

lognexus_note_attachA

Attach the current LogNexus state as a Git Note (refs/notes/lognexus) to a commit that already exists. Defaults to HEAD. Use when backfilling manually on commits created outside the commit engine, or repairing a missing note. Not for normal commits: lognexus_commit already attaches the note as part of the atomic operation, so attaching again is only needed when the note was lost.

lognexus_timelineA

Reconstruct the branch Journey Timeline against a base branch: commit list enriched with Git Notes, subtask IDs, tiers and Authored-by/Reviewed-by trailers, rendered as a Markdown table, JSON or a PR body draft. Use when preparing a pull request description or reviewing the subtask sequence of a branch. Not for judging compliance (use lognexus_audit, which reports violations rather than a narrative).

lognexus_auditA

Audit the branch commits against the LogNexus review gate: commit format, Authored-by trailer, Git Notes coverage, subtask file contracts, and author/reviewer separation including self-approval detection. Use when you need the pass/fail gate before merging or before opening a pull request. Not for producing the PR narrative (use lognexus_timeline); audit reports violations and never fixes them.

lognexus_telemetryA

Inspect local telemetry status, enable strictly local performance metrics (zero network calls), disable tracking, inspect the zero-PII local payload, generate telemetry markdown reports, or clear the metrics store. Use when measuring subtask duration, Git Notes coverage and estimated cost savings. Not for any form of upload: telemetry is local-only, stored in .lognexus/telemetry.json, and no data leaves the working directory.

Prompts

Interactive templates invoked by user choice

NameDescription
lognexus-planBreak a LogNexus issue down into ordered, verifiable subtasks with strict closed-delegation contracts delegated to the appropriate model tier.
lognexus-reviewAudit a diff or pull request against the LogNexus review gate before merging into main: contracts, verification, traceability and cross-model attribution.

Resources

Contextual data attached and managed by the client

NameDescription
LogNexus agent statePersistent LogNexus agent state (.lognexus/state.json): active issue, current subtask, completed subtasks and last synchronization timestamp.
Model-tier routing configurationMulti-model routing rules from .lognexus/routing.md, or the default tier taxonomy when the project has not been initialized.

TDQS

A4.3/5.0

Scored across 12 tools

Disambiguation4/5

The tools mostly have distinct purposes, and descriptions explicitly cross-reference alternatives. However, a couple of boundaries still require careful reading, especially lognexus_state_finish_task versus lognexus_commit with finishTask:true, and lognexus_status versus lognexus_state_get.

Naming Consistency4/5

All tools share the lognexus_ prefix and use snake_case, with clear state_* and note_* action subgroups. Minor deviations are the top-level bare nouns/verbs such as lognexus_status, lognexus_audit, and lognexus_telemetry.

Tool Count5/5

Twelve tools fit the workflow-management scope well. Each tool covers a meaningful state, commit, review, note, timeline, or telemetry operation without obvious filler.

Completeness4/5

The surface covers the core lifecycle: state inspection/sync, task set/finish/clear, commit creation, Git Notes, audit, timeline, and telemetry. Minor gaps exist around higher-level GitHub operations such as opening or merging a PR directly, though timeline and audit support the surrounding workflow.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues