WorkTrace MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| open_ai_key | Yes | Your OpenAI API key |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ask_contextA | Recover missing historical work context with one single comprehensive question. Use once per user request for prior goals, decisions, attempts, rationale, or activity. The service plans retrieval, searches screenshot-derived evidence, and synthesizes a cited answer. Do not call repeatedly to refine the same question; use the returned answer and inspect live state separately when current truth matters. Run independent live-state tools in parallel with this call when the host supports parallel tool execution. |
| get_eventA | Inspect one cited event only when provenance or artifact integrity materially matters. Prefer the answer returned by ask_context. Inspect at most one supporting event per user request unless the user explicitly asks for deeper evidence review. |
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 2 tools
Each tool has a distinct purpose: ask_context provides a synthesized answer about historical context, while get_event allows inspection of a specific event for provenance. There is no overlap in functionality.
Both tools follow a consistent verb_noun naming pattern (ask_context, get_event), making the intent clear and predictable.
Only two tools, which is slightly thin but appropriate for a focused utility that retrieves historical context and inspects events. The tools complement each other well.
The tools cover the core workflow of recovering context and verifying evidence. Minor gaps may exist (e.g., no direct search or listing of events), but the surface is sufficient for the stated purpose.