lockstep
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOCKSTEP_API_URL | No |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| notifyD | – |
| inboxD | – |
| ack_inboxD | – |
| queryD | – |
| askD | – |
| answerD | – |
| delegateD | – |
| completeD | – |
| propose_decisionD | – |
| ack_decisionD | – |
| register_dependencyD | – |
| decisionsD | – |
| whoownsD | – |
| consumersD | – |
| get_product_contextD | – |
| set_feature_contextD | – |
| refresh_decision_packD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 17 tools
With no descriptions, tools like 'inbox', 'ack_inbox', 'notify', 'query', and 'ask' have unclear boundaries and could easily be confused. Several names suggest overlapping actions (e.g., 'query' vs 'ask', 'decisions' vs 'propose_decision'), making it hard for an agent to reliably select the right one.
Naming conventions are mixed: single-word verbs (inbox, notify, query, ask) appear alongside verb_noun compounds (ack_inbox, propose_decision, refresh_decision_pack) and bare nouns (decisions, consumers). The pattern is inconsistent and does not follow a uniform grammatical structure, though some names like 'get_product_context' are descriptive.
17 tools is on the heavy side of the typical range (3-15) and feels borderline for a workflow-focused server. Without descriptions, it is plausible some tools could be consolidated, but the count is not extreme. It remains within a workable range.
The names suggest a workflow covering inbox management, decisions, notifications, and context, but obvious lifecycle operations are missing or unclear, such as rejecting a decision, updating a decision, or removing dependencies. There are no dead ends apparent, but the lack of descriptions makes it hard to confirm whether the surface fully covers the intended domain.