Skip to main content
Glama
Sign In

mFlow

by io.m-flow
OverviewDiscussionsAdmin

create_standalone_tasks

Create up to 50 tasks in one standalone project in a single call, optionally as a hierarchy — use this instead of create_standalone_task when breaking a plan into several tasks. To nest tasks in the same call, give the parent a localRef (any label unique within the call) and each child a parentRef with that label; parentId instead points at an already-existing task. Validation is all-or-nothing: if any task is invalid (unknown status/label/parent, unresolved or cyclic parentRef, duplicate localRef, missing title) NOTHING is created and every task gets a per-item result. Otherwise tasks are created parents-first in input order and appended to their status column in that order; if one fails mid-batch its children are skipped, never created orphaned. Returns {created, failed, rejected, results: [{index, localRef?, ok, taskId?, key?, error?}]} in input order. Not idempotent: if the call times out or errors, call list_standalone_tasks to see what already exists before retrying, or you will create duplicates.

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": {
      "projectId": "<projectId>",
      "tasks": "<tasks>"
    },
    "name": "create_standalone_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
tasksYesThe tasks to create, 1 to 50. Same field meanings as create_standalone_task, plus localRef/parentRef for hierarchy.
projectIdYesThe project to create the tasks in, from list_standalone_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A5/5.0
Behavior5/5

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

Although annotations only give readOnlyHint=false and destructiveHint=false, the description discloses rich behavioral detail: all-or-nothing validation, parents-first creation order, child-skipping on mid-batch failure, per-item results, and non-idempotence. This goes far beyond the annotations and tells the agent exactly what to expect.

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 long but every sentence carries essential operational information. It is front-loaded with the core use case, then proceeds through validation, ordering, failure behavior, return shape, and idempotency without filler.

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?

For a complex batch mutation with 2 required parameters, hierarchy semantics, failure modes, and no output schema, the description is complete. It covers return structure, per-item results, validation rules, ordering, parent-child handling, and retry guidance, so an agent can invoke and interpret the result correctly.

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

Parameters5/5

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

Schema coverage is already 100%, so the baseline is 3, but the description adds meaningful semantics beyond the schema: localRef can be any unique label, parentRef may appear before or after its parent, parentId points to an existing task, and tasks default to the 'todo'-category status. It also clarifies the relationship between the three parent-related fields.

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 opens with a specific verb and resource: 'Create up to 50 tasks in one standalone project in a single call.' It explicitly distinguishes itself from create_standalone_task by stating when to use this bulk variant, so an agent can immediately tell the two apart.

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?

It names the alternative explicitly: 'use this instead of create_standalone_task when breaking a plan into several tasks.' It also gives precise guidance for hierarchy construction (localRef vs parentRef vs parentId) and for retry behavior after timeouts, telling the agent to call list_standalone_tasks before retrying.

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

All mFlow toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources