MCP Work History Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| log_activityC | Log AI tool activity to a daily worklog file with comprehensive metrics |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'log_activity' follows a clear verb_noun pattern.
A single tool is too few for a server with a broad purpose like 'Work History,' which suggests tracking or managing activities. This minimal set severely limits functionality and likely leaves significant gaps in coverage.
The server is severely incomplete for a work history domain. It only allows logging activity but lacks essential operations like retrieving, updating, deleting, or querying logs, making it impossible for agents to perform basic CRUD workflows.