Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
STRATEGY_DB_URLNoWhere the store lives. Settings are read from the process environment first, then ~/.env, then the default. If STRATEGY_DB_URL is set and cannot be opened, the CLI fails and says so.SQLite at ~/.strategy/store.db
STRATEGY_EXPORT_PATHNoJSONL backup target. Settings are read from the process environment first, then ~/.env, then the default.~/.strategy/positions.jsonl

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

A strategy store: positions under the five Playing to Win boxes. list shows the strategy, show one position and its evidence; adopt, reject and evidence_add decide on one; add puts a new one in a box. A store can hold several strategies (cascades): cascade_list names them, and list and add take one as cascade. To sort, triage or prioritise tasks in any tracker: call list first and judge each task against the ADOPTED positions only; if none is adopted, stop and say so. Keep what serves one, park what doesn't, and name the position that decided it. Ask before changing anything in the tracker, and never delete a task. Undecided positions are not yet the strategy.

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
listA

The strategy: every current position under its Playing to Win box, aspiration first; optional cascade (a key from cascade_list) for one strategy, or "-" for the positions no cascade holds. To sort, triage or prioritise tasks in any tracker: call list first and judge each task against the ADOPTED positions only; if none is adopted, stop and say so. Keep what serves one, park what doesn't, and name the position that decided it. Ask before changing anything in the tracker, and never delete a task.

showC

One position: its box, whether it is adopted, and the evidence noted on it.

adoptC

Adopt a position: I hold this. Dates it today.

rejectC

Reject a position: I do not hold this. A reason is required.

evidence_addC

Note something observed that bears on a position; optional stance: supports | opposes | complicates.

addB

Add a position into a box — 1 aspiration, 2 where to play, 3 how to win, 4 capabilities, 5 management systems (number or name). It arrives undecided. Optional cascade: add it to that strategy.

cascade_listA

The strategies (cascades) in this store: key, name, the question each answers, and how many positions it holds. Pass a key as cascade to list or add.

cascade_createB

Start a new strategy (cascade) by name, with the question it answers (optional). It starts empty.

cascade_renameB

Rename a cascade, or change the question it answers. Its key stays the same.

cascade_deleteA

Delete a cascade. Its positions are kept, with their decisions and evidence, as unassigned positions (list with cascade "-").

Prompts

Interactive templates invoked by user choice

NameDescription
triageSort tasks in any tracker against the adopted positions: keep or park, with the position that decided it. Optional: which tasks (a project, a filter, a list).

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.1/5.0

Scored across 10 tools

Disambiguation4/5

Most tools target clearly different operations: list/show for reading positions, add for creation, adopt/reject for decisions, evidence_add for evidence, and cascade_* for strategy containers. The only mild overlap is between list and cascade_list, and between list and show, but the descriptions clarify resource and scope well enough.

Naming Consistency3/5

Core position operations are bare verbs (list, show, add, adopt, reject), while cascade operations use a noun_verb prefix and evidence_add uses a different noun_verb ordering. It remains readable, but there is no single predictable naming pattern across the whole set.

Tool Count5/5

Ten tools is well within a healthy range for this domain, and each tool maps to a distinct operation in the strategy/cascade model. None feels redundant or purely decorative.

Completeness3/5

The surface covers position creation/reading, decisions, evidence, and full cascade CRUD. However, there is no way to update or delete a position (for example, editing its text or moving it between Playing to Win boxes), which is a notable lifecycle gap.

Maintenance

ActivitySlowing
ResponsivenessNo recent community issues