Skip to main content
Glama

run_workflow

Read-onlyIdempotent

Execute structured workflows for product, engineering, business, and operations tasks. Automatically applies your personal memories and identity to guide each process.

Instructions

Run a Purmemo workflow — structured, memory-powered processes for product, engineering, business, and operations tasks. Your relevant memories and identity are automatically loaded to personalize every workflow.

WHEN TO USE THIS TOOL:

  • User wants to write a PRD, debug an issue, plan a sprint, review code, or any structured task

  • User describes a goal but doesn't know the exact process ("I want to ship a feature")

  • User asks for strategic advice, design guidance, or operational help

  • User says "help me", "guide me", "walk me through", or describes a business/product/engineering need

AVAILABLE WORKFLOWS (pass the workflow name, or describe what you need): Product: prd, roadmap, story, design, feedback Strategy: ceo, growth, metrics, intel Engineering: debug, review, deploy, incident Operations: sprint Content: copy

EXAMPLES: run_workflow(workflow="prd", input="notification system for mobile app") run_workflow(workflow="debug", input="TypeError: Cannot read property 'map' of undefined in Timeline") run_workflow(input="production is down, users can't save memories") → auto-routes to incident run_workflow(input="what should I focus on this week?") → auto-routes to sprint run_workflow(input="how's the business doing?") → auto-routes to metrics

DO NOT use this tool for: simple memory recall (use recall_memories), saving conversations (use save_conversation), or finding related discussions (use discover_related_conversations).

If no specific workflow is named, the system auto-routes based on the user's intent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflowNoWorkflow name (e.g., "prd", "debug", "sprint"). Use list_workflows to see all available options including custom workflows. Optional — if omitted, auto-routes from input.
inputYesWhat you want to accomplish, the problem to solve, or context for the workflow.
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint. The description adds context about automatic loading of memories and identity, auto-routing when no workflow is specified, and personalization. No contradictions with annotations.

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 clear sections (purpose, when to use, available workflows, examples, exclusions). It is appropriately sized for the complexity, though slightly verbose. Front-loaded with the core purpose.

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

Completeness4/5

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

The description covers workflow types, examples, and when to use. However, it does not explicitly describe the return value/response format after running a workflow. Given no output schema, this is a minor gap, but otherwise the description is thorough for the tool's complexity.

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

Parameters4/5

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

Schema coverage is 100% with brief descriptions for both parameters. The description adds value by listing available workflow names, providing examples, and explaining auto-routing behavior when 'workflow' is omitted. This goes beyond the schema alone.

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 the tool runs Purmemo workflows, listing specific workflow categories and examples. It distinguishes from siblings by explicitly stating when not to use (memory recall, save conversation, discover related conversations).

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

Usage Guidelines5/5

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

The description has explicit sections: 'WHEN TO USE THIS TOOL' with concrete scenarios, and 'DO NOT use this tool for' with sibling alternatives. This provides clear context for when to choose this tool over others.

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/purmemo-ai/purmemo-mcp'

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