hearthsmith
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TYPESAFE_API_KEY | No | API key for the typesafe decide backend (requires early-access 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 |
|---|---|
| hearthsmith_tasks_listA | List tasks. state: open | done | blocked | delegated | all. project filters by hyperpanes project id/name. |
| hearthsmith_tasks_addB | Add a task. due is ISO date/datetime (local). project is a hyperpanes project id or name. |
| hearthsmith_tasks_doneA | Mark a task done. Accepts an id prefix. |
| hearthsmith_tasks_blockB | Mark a task blocked (the pet stops nagging about it). |
| hearthsmith_tasks_snoozeC | Snooze nagging for a task. |
| hearthsmith_nags_recentB | What the blacksmith said recently, with the decision that drove it. |
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 6 tools
Each tool targets a distinct action: adding, listing, marking done, blocking, snoozing, and viewing recent nags. No two tools have overlapping purposes, so an agent can easily select the correct one.
Most tools follow the pattern hearthsmith_tasks_<verb> (add, list, done, block, snooze), but 'done' is a past participle rather than a verb, and 'nags_recent' uses an adjective instead of an action. The prefix is consistent and the deviations are minor.
Six tools is well-scoped for a task management server with a nagging feature. Each tool fills a clear role, and the count feels neither thin nor bloated.
The surface covers the core lifecycle: create (add), read (list), and multiple state updates (done, block, snooze). Missing a general edit or delete, but the domain does not clearly require them, and the existing operations cover the main workflow without dead ends.