Skip to main content
Glama
yurikaza
by yurikaza

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AGENT_WORK_STATE_DIRNoWhere sessions are stored. Defaults to <project root>/.agent-work.<project root>/.agent-work
AGENT_WORK_PROJECT_ROOTNoProject root for new sessions. Defaults to server working directory.server working directory

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": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
start_sessionA

Start a work session for a project goal. mode "outside" = bounded autonomous run (no human; requires budgetMinutes, the total wall-clock autonomy for the whole session, not per task). mode "desk" = human in the loop. Returns a sessionId handle (pass it to every other tool), a repository snapshot and analysis instructions. Next: analyze the project, then update_work_graph.

list_sessionsA

List recorded sessions (newest first) with state, budget and open decision counts. Use to find a session to inspect or resume.

get_sessionA

Current state, mode, budget, unit counts, in-flight units and run history of one session.

get_phaseA

The phase goal, exit criteria and constraints this session owns, progress toward it, and the project context recorded during analysis.

pause_sessionA

Pause an active session. Stops the budget clock and keeps in-flight claims. Optional handoff notes.

resume_sessionA

Resume a paused, halted or interrupted session from its handoff. Optionally switch mode (desk/outside) and add budget. Recovers in-flight units of an interrupted run (they return to pending with their checkpoints). Returns the handoff.

stop_sessionA

End the current run. In-flight units are released with their checkpoints and the session is classified (resumable, waiting_for_human, blocked or completed). markFailed: true ends it permanently as failed. Returns the final report.

get_work_graphA

Units with status, derived readiness and root causes (decision:, blocker:, failure:, cancelled:), plus dependency edges. Filter: all | remaining | ready | in_progress | done.

update_work_graphA

Add or update units (upsert by id), cancel or reopen units, and record project context (summary, key files, commands). The first call submits the initial plan. Rejected as a whole if ids, references or dependencies are invalid or cyclic. Units added after the initial plan need a rationale. Never add work only to use remaining budget.

next_workA

Re-evaluate the graph, budget and policy and claim the next work. action "execute" = do the dispatched units (direct, or parallel with subagents when justified); "wait" = finish in-flight units first; "plan" = analysis/graph needed; "stop" = the run is over (budget spent, waiting for human, blocked, or completed). Call after every report_work. Only "stop" ends an OUTSIDE_MODE run.

report_workA

Report a claimed unit: progress (checkpoint), completed (requires validation evidence), failed, blocked (requires blocker), or released. Completed with failing checks counts as a failed attempt. Then call next_work: a finished unit never ends the session.

request_decisionA

Queue a question that needs human judgment (architecture, product, scope, security...). Never guess instead. Affected units wait; everything else continues. Returns impact and the independent work that can proceed. Does not block and does not wait for an answer.

get_decisionsA

The decision queue, most blocking first, with why each matters, options, the agent suggestion and blocked/independent work.

record_decisionA

Record a decision made by a human (or withdraw a question that no longer applies). Only call with the human's explicit answer. Refused while an OUTSIDE_MODE run is active. Releases the units the decision gated.

get_handoffA

Exactly where to pick up: state and why, decisions needed (most blocking first), in-flight checkpoints, ready units, blocked units with causes, completed work, project context, repository state and ordered next actions. Start DESK_MODE here.

get_session_reportA

Session report: outcome, budget used and why any was left unused, completed work with validation evidence, unresolved work, decisions, parallel dispatches and their rationale, scope added mid-session, and next steps.

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 16 tools

Disambiguation5/5

Each tool targets a distinct aspect of session and work-graph management, with clear separation between session lifecycle (start/pause/resume/stop), state inspection (get_session, get_phase, get_handoff, get_session_report), work graph manipulation (get/update_work_graph, next/report_work), and decision handling (request/get/record_decision). No two tools appear to do the same thing.

Naming Consistency5/5

All 16 tools follow a consistent snake_case verb_noun pattern (e.g., pause_session, update_work_graph, request_decision). The verbs are imperative and match the action taken, with no mixing of conventions or vague generic names.

Tool Count4/5

At 16 tools, the set is slightly above the typical 3–15 range, but each tool serves a distinct and necessary function for managing complex agent work sessions, covering lifecycle, graph, decisions, and reporting. The count feels justified rather than bloated.

Completeness5/5

The tool surface fully covers the session lifecycle (start, pause, resume, stop), work graph operations (create/update, query, claim, report), decision management (request, query, record), and reporting (handoff, session report). No obvious dead ends or missing operations for the stated domain.

Maintenance

ActivityMaintained
ResponsivenessNo issues