Skip to main content
Glama
108yen

task-orchestrator-mcp

by 108yen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
FILE_PATHNoPath to JSON file for task storage

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
createTaskA

Create a new task with optional parent and index positioning.

This tool initiates a new workflow for handling user requests. To manage tasks, you MUST always run this tool first. The workflow is as follows:

  1. Create tasks with the provided name and optional description. Tasks are organized in a hierarchical structure where subtasks can be created by specifying parentId.

  2. Tasks are ordered by their position in the parent's tasks array. Use insertIndex to specify position (defaults to end).

  3. After task creation, you MUST call the startTask tool to begin processing the task.

  4. When the task is completed, call the completeTask tool with the task ID and resolution details.

  5. If the following task is assigned, execute it by calling the startTask tool again.

  6. Repeat this cycle until all tasks are completed.

getTaskB

Get a task by its ID

listTasksA

List tasks from hierarchical structure, optionally filtered by parentId. Returns root tasks if no parentId specified, or direct children of specified parent task.

updateTaskC

Update an existing task

deleteTaskC

Delete a task by its ID

startTaskB

Start a task (change status to in_progress)

  1. Run this tool to start the task.

  2. When the task is complete, call the completeTask tool to complete the task.

completeTaskB

Complete a task and get the next task to execute. To start the next task, execute startTask.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
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

TDQS

A3.6/5.0

Scored across 7 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: createTask initiates tasks, getTask retrieves a single task, listTasks retrieves multiple tasks, updateTask modifies tasks, deleteTask removes tasks, startTask begins task execution, and completeTask finishes execution and triggers the next step. There is no overlap or ambiguity between these functions.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with camelCase styling (e.g., createTask, getTask, listTasks, updateTask, deleteTask, startTask, completeTask). This uniformity makes the tool set predictable and easy to understand.

Tool Count5/5

With 7 tools, this server is well-scoped for task orchestration, covering the full lifecycle from creation to completion. Each tool serves a necessary function without redundancy, making the count ideal for the domain.

Completeness5/5

The tool set provides complete CRUD and lifecycle coverage for task management: create, read (get and list), update, and delete operations, plus start and complete actions for execution flow. There are no gaps that would hinder an agent from managing tasks end-to-end.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources