workflow-hints
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WORKFLOW_HINTS_DATA_DIR | No | Directorio alternativo para state/config. |
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": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hints_record_eventB | Record a Cursor workflow activity event and return optional nudge context. |
| hints_get_contextB | Get today's workflow summary as agent context. |
| hints_get_daily_summaryA | Get structured counters and timing for today. |
| hints_set_preferencesC | Update local hint thresholds and notification settings. |
| hints_dismiss_nudgeB | Dismiss nudges for today or mark a specific nudge type as sent. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| hints-today | Today's workflow counters and timing |
TDQS
Scored across 5 tools
Most tools map to distinct actions, but hints_get_context and hints_get_daily_summary both return today's workflow data and could be easily confused. The other three tools are clearly separated by their record, preference, and dismissal purposes.
All tools use the consistent hints_ prefix with clear verb_noun snake_case names like record_event, set_preferences, and dismiss_nudge. The naming pattern is predictable and easy to follow.
Five tools is well-scoped for a workflow-hints server. Each tool covers a distinct part of the workflow lifecycle without unnecessary bloat or redundancy.
The set covers event recording, context retrieval, daily summaries, preference updates, and nudge dismissal, forming a complete workflow loop. A minor gap is the lack of an explicit get-current-preferences endpoint, but agents can likely work around this.