samskriti-project
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SAMSKRITI_HOME | No | Override the default data directory (~/.samskriti/) | |
| SAMSKRITI_PROJECT_DB | No | Override the default database path |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| record_project_entryB | Stores a structured project-state entry (goal, update, decision, convention, bug, task, rejected_idea). |
| get_project_stateB | Returns a concise, readable summary of project state, grouped by category. |
| search_project_stateB | Search the project state ledger using a simple keyword query. |
| update_project_entryA | Update an existing project entry's title, content, or status. |
| list_projectsA | Returns a list of all known projects tracked by Samskriti V1. |
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 5 tools
Each tool has a distinct purpose: summarizing state, listing projects, recording entries, searching, and updating. No overlapping functionality.
All tool names follow a consistent verb_noun pattern (e.g., get_project_state, record_project_entry), ensuring predictability.
With 5 tools, the server covers essential operations without being overwhelming or insufficient for project state management.
Covers core operations (list, get, record, search, update) but lacks explicit project creation and deletion, which may be minor gaps.