agent-prompt-capture
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APC_HOME | No | The runtime directory. Default ~/.agent-prompt-capture, created mode 0700. | ~/.agent-prompt-capture |
| APC_DEBUG | No | Set to '1' for DEBUG level logging and a stderr handler in addition to apc.log. | 0 |
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 |
|---|---|
| list_promptsA | List captured prompts, newest first (oldest first is not offered; page with |
| search_promptsA | Full text search over the captured prompt text, best match first. |
| get_promptA | Fetch one captured prompt by its |
| prompt_statsA | Cheap prompt counts and character totals - no time analysis. Reach for time_summary instead when the question is about time. |
| list_sourcesA | Which capture sources have prompts, how many, and the first/last timestamp for each. Takes no arguments. Call it first when you are unsure what is being captured at all, or to check whether a source has gone quiet. |
| list_sessionsA | List agent/conversation sessions, most recently active first, with their project, first/last timestamp and prompt count. Use a returned |
| time_summaryA | Where the user's time went. THE tool for any question about time use, focus or workload. Returns per-group |
| activity_timelineA | The shape of the user's activity over time: contiguous buckets, each with |
| daily_digestA | Everything worth knowing about one local calendar day: first/last activity, |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| recent_prompts | The last 50 captured prompts as JSON. |
| stats_summary | Per-source prompt counts for the last 7 days. |
| digest_today | Today's activity digest: sessions, context switches and top terms. |
TDQS
Scored across 9 tools
Each tool has a clear, distinct role: list_prompts/search_prompts/get_prompt for raw access, list_sources/list_sessions for metadata, and the four analytics tools each target a different slice (timeline buckets, counts, time-use groups, single-day digest). Even the overlapping time-related tools have explicitly differentiated use cases.
The retrieval tools follow a consistent verb_noun pattern (list_prompts, list_sources, list_sessions, search_prompts, get_prompt), but the analytics tools use plain noun names (activity_timeline, prompt_stats, time_summary, daily_digest). This is predictable and readable, but not a fully uniform convention across the set.
Nine tools is well-scoped for a prompt-capture and analysis server, covering enumeration, search, single-record fetch, metadata discovery, and multiple analytic views without redundancy or bloat.
The surface covers the full read-side lifecycle: discover sources/sessions, browse/search/fetch prompts, and analyze activity over time at both aggregate and per-day granularity. For a read-only capture server, there are no obvious gaps.