Skip to main content
Glama

workflow_mode

Manage workflow modes, get contextual suggestions, and view usage analytics. Switch between focused tool groups to reduce clutter and improve productivity.

Instructions

[HINT: Workflow mode management. action=focus|suggest|stats. Unified workflow operations.]

Unified workflow mode management tool consolidating focus, suggestions, and usage statistics.

Actions:

  • action="focus": Manage workflow modes and tool groups

  • action="suggest": Get mode suggestions based on context/usage

  • action="stats": View tool usage analytics and patterns

📊 Output: Mode status, suggestions, or usage statistics 🔧 Side Effects: May update tool visibility and send notifications ⏱️ Typical Runtime: <100ms

Modes (focus action):

  • daily_checkin: Health + overview (9 tools, 82% reduction)

  • security_review: Security-focused (12 tools, 77% reduction)

  • task_management: Task tools only (10 tools, 81% reduction)

  • sprint_planning: Tasks + automation + PRD (15 tools, 71% reduction)

  • code_review: Testing + linting (10 tools, 81% reduction)

  • development: Balanced set (25 tools, 52% reduction) [default]

  • debugging: Memory + testing (17 tools, 67% reduction)

  • all: Full tool access (52 tools)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNo"focus" to manage modes/groups, "suggest" for suggestions, "stats" for analyticsfocus
modeNoWorkflow mode to switch to (focus action)
enable_groupNoSpecific group to enable (focus action)
disable_groupNoSpecific group to disable (focus action)
statusNoIf True, return current status without changes (focus action)
textNoOptional text to analyze for mode suggestion (suggest action)
auto_switchNoIf True, automatically switch to suggested mode (suggest action)
ctxNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden. It discloses side effects ('may update tool visibility and send notifications'), typical runtime (<100ms), and output type. However, it does not detail permissions, reversibility, or failure modes, leaving some opacity for a state-modifying tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with sections, bullet points, and emoji cues, making it scannable. However, it is somewhat verbose with redundant elements like the HINT prefix and mode list that could be streamlined.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the high schema coverage, presence of output schema, and moderate tool complexity, the description covers essential aspects: actions, modes, output type, side effects, and performance. No critical gaps are evident.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 88%, so the schema already describes most parameters. The description adds context for actions and modes but does not significantly enhance understanding of individual parameters beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it is a unified workflow mode management tool, listing specific actions (focus, suggest, stats) and modes. This distinguishes it from sibling tools like infer_session_mode and context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides action-specific usage (focus for modes/groups, suggest for suggestions, stats for analytics) and lists available modes for the focus action. However, it does not explicitly state when not to use the tool or mention alternatives, so it lacks exclusion guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/davidl71/project-management-automation'

If you have feedback or need assistance with the MCP directory API, please join our Discord server