Skip to main content
Glama
Sign In
OpenMesha

OpenMesha

by ANAMIZED
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

create_workflow

Create specialist agents and run a sequential multi-agent workflow for goals needing multiple roles, with a shared budget across planner and worker.

Instructions

Create specialist agents and run a sequential multi-agent workflow.

Default roles are planner then worker, sharing budget_usd. Use when a goal needs more than one agent. Do not use to run a single existing agent (run_task). Side effects: creates agents + tasks and marks the workflow completed.

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": {
      "name": "<name>",
      "goal": "<goal>"
    },
    "name": "create_workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalYesShared goal given to each specialist agent.
nameYesWorkflow name.
agentsNoRole names. Default planner then worker.
budget_usdNoShared USD budget split across roles.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / agents / description
      Added value: +"Role names. Default planner then worker."
    • removedInput schema / properties / agents / title
      Removed value: -"Agents"
    • addedInput schema / properties / budget_usd / description
      Added value: +"Shared USD budget split across roles."
    • removedInput schema / properties / budget_usd / title
      Removed value: -"Budget Usd"
    • addedInput schema / properties / goal / description
      Added value: +"Shared goal given to each specialist agent."
    • removedInput schema / properties / goal / title
      Removed value: -"Goal"
    • addedInput schema / properties / name / description
      Added value: +"Workflow name."
    • removedInput schema / properties / name / title
      Removed value: -"Name"
    • removedInput schema / title
      Removed value: -"create_workflowArguments"
    • removedOutput schema / title
      Removed value: -"create_workflowDictOutput"
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full disclosure burden. It clearly lists side effects: 'creates agents + tasks and marks the workflow completed', and explains default role behavior and budget sharing. It could mention reversibility or permission requirements, but the key side effects are present.

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?

Four short sentences with no fluff. The core purpose is front-loaded, followed by default behavior, usage guidance, and side effects. Every sentence earns its place.

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?

For a workflow-creation tool, the description covers purpose, defaults, side effects, and when not to use it. An output schema exists, so return value documentation is not required here. It lacks some details like idempotency or auth, but those are not essential for initial selection and invocation.

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%, so the baseline is 3. The description adds meaningful context beyond the schema by explaining that 'agents' defaults to planner then worker and that 'budget_usd' is shared across roles. This helps the agent understand how the parameters relate to each other.

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 states a specific action ('Create specialist agents and run a sequential multi-agent workflow') and clearly identifies the resource. It further distinguishes itself from run_task, making it easy for an agent to know this is the multi-agent orchestration tool.

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?

Explicitly says 'Use when a goal needs more than one agent' and 'Do not use to run a single existing agent (run_task)'. This gives both positive and negative usage conditions and names the alternative tool.

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

Deploy Server

Other Tools