HUMMBL MCP Server

Start Guided Workflow

start_workflow

Begin a guided multi-turn workflow to systematically solve problems using validated mental models for root cause analysis, strategy design, or decision making.

Instructions

Begin a guided multi-turn workflow for systematic problem-solving using Base120 mental models.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workflow_name": "<workflow_name>",
      "problem_description": "<problem_description>"
    },
    "name": "start_workflow"
  }
}

Input Schema

Name	Required	Description
`workflow_name`	Yes	Which workflow to start
`problem_description`	Yes	Brief description of your problem or goal
`session_id`	No	Optional session ID for state persistence

Output Schema

Name	Required	Description	Default
`workflow`	Yes
`displayName`	Yes
`problemDescription`	Yes
`currentStep`	Yes
`totalSteps`	Yes
`transformation`	Yes
`guidance`	Yes
`suggestedModels`	Yes
`questions`	Yes
`nextAction`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.0.3May 4, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It mentions 'multi-turn' but fails to explain that the tool returns a session_id for continuation, the expected follow-up calls, or any side effects. A guided workflow initiation requires more behavioral context.

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

Conciseness5/5

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

The description is a single sentence that is front-loaded with the key action and purpose. No unnecessary words, making it concise and to the point.

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

Completeness2/5

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

Given the complexity of a guided multi-turn workflow, the description is incomplete. It does not explain the return value (despite an output schema existing), how to continue the workflow, or what to expect after starting. The presence of sibling tools like continue_workflow implies a sequence, but the description does not connect them.

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 description coverage is 100%, so baseline is 3. The description adds no additional meaning to the parameters beyond what the schema provides, such as elaborating on the enum values or the format of problem_description.

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 verb 'Begin', the resource 'workflow', and specifies it is a guided multi-turn process using Base120 mental models. It distinguishes from sibling tools like continue_workflow and list_workflows.

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

Usage Guidelines3/5

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

The description implies usage for starting a workflow but does not explicitly state when to use versus alternatives like continue_workflow or list_workflows. No exclusions or prerequisites are mentioned.

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

Deploy Server