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

Tools

Functions exposed to the LLM to take actions

NameDescription
infoC

Startup orientation and compact sprint discovery before binding to one sprint.

sprint_newC

Start a sprint with explicit git_dir and a worktree-scoped, uncommitted data_dir; returns orientation.

sprint_resumeB

Resume an existing sprint by binding this MCP session to an existing git_dir and data_dir without creating a sprint.

sprint_detachC

Detach this MCP session from its current Sprinty binding and stop the dashboard.

sprint_closeC

Re-check all gates, write the canonical SemVer changelog, and close the sprint; force bypasses only executable gate failures.

sprint_archiveB

Archive the sprint with a recovery reason, bypassing normal close gates.

overviewC

Compact sprint overview: title, details, notes, artifacts, and subsprint counts.

nextD

Compact work window for choosing the next item.

subsprint_newC

Create a subsprint (description, goals, gates).

subsprint_getC

Read one subsprint with compact item rows.

subsprint_listC

List subsprints with compact rows.

item_addC

Add an atomic item (bounded title, bounded description, code locations, gates — all required; gate_timeout_ms defaults to 5000 and null disables it).

item_getC

Read one item with full untruncated detail.

item_updateA

Update an item by id: metadata, open-item gates/timeout, completed-item commit_id, and/or dependency ids.

item_doneA

Resolve an item as completed with a commit id and a semver changelog verb (added/fixed/changed/removed/deprecated/security). Sprinty runs the item's executable gates itself; only manual gates take agent-supplied gate_results.

item_splitC

Resolve an item as split, creating a seeded subsprint atomically.

item_deprecateA

Resolve an item as deprecated with a reason, or drop a whole subsprint by passing its id (its open items are deprecated too).

note_addB

Add a note to a specific item id. Notes are not substitutes for item_add(); create items for trackable work.

note_getC

Read notes attached to an item id.

note_listC

List notes for an item as compact rows.

note_updateD

Update a note by note id.

artifact_addC

Attach a file path to the sprint, optionally related to item ids.

artifact_getC

Read one artifact by id.

artifact_listB

Page through active sprint artifacts as compact newest-first rows.

artifact_updateC

Update an artifact by id.

searchC

Regex search over sprint text with character context around each match.

changelogB

Preview or export the current SemVer Markdown changelog and return only its path; sprint_close writes the canonical changelog automatically.

dashboard_infoA

Return the current dashboard URL and port without starting or restarting it.

dashboard_restartC

Restart the follow-along dashboard and return its URL and port.

agent_listC

List named agents, activity state and claim counts; paginated and token-free.

items_claimedB

List current item claims, optionally only yours; includes timing, progress and stall reasons.

agent_attachC

Attach an independent named agent; retain its returned token for shared connections.

agent_detachC

Detach only this agent and release its claims.

agent_heartbeatC

Report activity during long tasks; does not reset item progress or stall completion counts.

item_claimB

Claim an open item. Optional force is a 1–500 character explanation that overrides existing ownership immediately, without activity or stall conditions; recorded in handover history.

item_releaseC

Release your claim for another agent.

item_takeoverB

Take over a potentially stalled claim with an explanation, or pass force as a 1–500 character explanation to override ownership immediately without activity or stall conditions.

item_progressC

Record meaningful progress on your claimed item.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
how-to-run-a-sprint
using-sprinty

TDQS

C2.4/5.0

Scored across 38 tools

Disambiguation3/5

The domain prefixes (item_/subsprint_/note_/artifact_/agent_/sprint_/dashboard_) make most tools separable, but item_claim and item_takeover genuinely overlap since item_claim's `force` argument already overrides ownership immediately, duplicating takeover's force behavior. sprint_close vs sprint_archive and the family of compact readers (info, overview, next, subsprint_get, items_claimed) also require reading descriptions carefully to choose correctly.

Naming Consistency4/5

Strong, mostly consistent snake_case with resource prefixes and a predictable verb set (add/get/list/update/done/split/deprecate/new/resume). Minor deviations only: a handful of bare names (info, next, overview, search, changelog) and one plural outlier (items_claimed) break the verb_noun pattern.

Tool Count2/5

38 tools is heavy for a single sprint-tracking server, well past the comfortable 3-15 range. Several clusters could be consolidated (claim/release/takeover/progress as one item lifecycle tool; dashboard_info/dashboard_restart; sprint_close/sprint_archive), so the surface feels padded rather than scoped.

Completeness3/5

Sprint lifecycle, subsprints, items, claims, notes, artifacts, agents, and changelog are broadly covered, but there are real gaps: no delete for notes or artifacts (only add/get/list/update), and no generic item_list — items are only reachable via subsprint_get or `next`. Agents will hit dead ends when they need to remove a stale note/artifact or enumerate items directly.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues