agenthelm
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENTHELM_PROJECT | Yes | Your project name | |
| AGENTHELM_CONNECT_KEY | Yes | Your AgentHelm connect key (e.g., ahe_live_YOUR_KEY_HERE) |
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 |
|---|---|
| get_contextA | Retrieves relevant, ranked context from the Project Brain using semantic context selection. Useful when starting a task, resolving design questions, or looking up project standards. |
| propose_knowledgeA | Submits a Knowledge Proposal containing newly discovered or updated project design, decisions, schema changes, or API specifications. The proposal enters a validation queue before being compiled into the Project Brain. |
| get_historyA | Retrieves version history, diffs, blame, or show details for the Project Brain. Allows reviewing exactly who proposed what, what files changed, what conflicts occurred, and when. |
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 3 tools
Each tool targets a distinct operation on the Project Brain: retrieval of context, submission of new knowledge, and querying history. There is no overlap in purpose.
All tool names follow a consistent verb_noun pattern in snake_case (get_context, propose_knowledge, get_history). The repetition of 'get' is acceptable as it indicates retrieval operations.
With only 3 tools, the server is scoped for a focused knowledge management function. While minimal, each tool serves a clear purpose and the count is appropriate for the domain.
The tools cover retrieval, submission, and history, but lack direct update or delete operations for knowledge items. Updates could be handled via new proposals, but that introduces overhead and gaps.