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
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
start_effortC

Create an effort from a plan artefact and an initial PERT estimate.

add_sliceC

Add a slice. One added while the effort is active is scope growth.

close_sliceC

Close a slice against its pull request.

drop_sliceC

Drop a slice that turned out to be unnecessary.

rename_sliceD

Rename a slice.

clock_inC

Start an interval. Refused if one is already open.

clock_outC

Close the open interval.

annotate_intervalC

Attach meeting participants or a note to an interval after the fact.

repair_intervalB

Correct an interval's bounds. Appends; never rewrites.

record_absenceC

Declare time not spent working. Retroactive by design.

record_revisionC

Record a revised estimate, typically when a slice is inserted.

record_final_planD

Record the final plan and the counterfactual estimate against it.

harvest_commitsC

Copy commit metadata from a working tree into the store.

record_landed_commitC

Record the durable commit that landed on the default branch.

remap_commitsC

Map a rewritten commit id onto its replacement.

finish_effortC

Mark an effort done.

reference_effortsC

Prior efforts with their summaries and estimates, for comparison. No actuals.

currentB

What is clocked in, and since when.

effort_tableC

One near-raw row per effort: estimates, wall hours, slice counts.

effort_detailC

One effort's full event history.

summaryB

Aggregate calibration, or an honest refusal when there is too little data.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.8/5.0

Scored across 21 tools

Disambiguation5/5

Every tool has a clearly distinct purpose. Even overlapping domains like commits (harvest, record, remap) and intervals (clock, annotate, repair) are separated by specific actions and targets. No two tools could be easily confused for the same operation.

Naming Consistency4/5

The majority of tools follow a consistent verb_noun pattern (e.g., repair_interval, start_effort, add_slice). A few query tools are named as nouns (current, summary, effort_table, effort_detail), which is a minor deviation but still readable and sensible for retrieval operations.

Tool Count4/5

With 21 tools, the surface is substantial but justified by the domain's complexity—covering efforts, intervals, slices, commits, estimates, and queries. Each tool adds distinct functionality, though the count is on the higher end and could feel heavy for simpler use cases.

Completeness5/5

The toolset provides comprehensive lifecycle coverage: starting and finishing efforts, managing slices (add/close/drop/rename), tracking time (clock in/out, absence), revising estimates, recording commits, and rich reporting (current, table, detail, summary). No obvious gaps or dead ends are apparent.

Maintenance

ActivityMaintained
ResponsivenessNo issues