Skip to main content
Glama
greendwin

tasker

by greendwin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
create_taskA

Create a root task or subtask (when parent is given).

edit_taskC

Update a task's title, description, or slug.

start_taskC

Mark a task as in-progress.

review_taskC

Mark a task as in-review (submit for review).

reset_taskA

Reset a task back to pending.

Use force=True to reset all non-pending subtasks.

cancel_taskB

Cancel a task. Use force=True to cancel all open subtasks.

finish_taskA

Mark a task as done. Use force=True to close all open subtasks.

list_tasksA
List root tasks as compact lines: ``<sign> <id>  <title> (...)``.

Status signs: ``.`` pending, ``~`` in-progress, ``?`` in-review,
``x`` done, ``-`` cancelled. A trailing ``(...)`` marks a task that has
a body -- view it for the full detail.

Args:
    todo: If True, list only tasks from the TODO list.
view_tasksA

View tasks by IDs as trimmed markdown.

Each task renders as ``# <id>: <full title>`` followed by ``status:`` /
``parent:`` metadata lines (``parent:`` omitted for root tasks), the
verbatim task body, and a ``## Subtasks`` checklist reusing the compact
line format. A bad/deleted/unknown ref becomes a ``# <ref>: <error>`` stub
instead of failing the batch. Blocks are joined by ``\n\n---\n\n``.

Use this instead of reading task files from disk.

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.7/5.0

Scored across 9 tools

Disambiguation5/5

Each tool targets a distinct operation on tasks: create, edit, list, view, and status transitions (start, review, finish, cancel, reset). No two tools have overlapping purposes.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in snake_case (e.g., cancel_task, create_task). No mixing of styles or irregularities.

Tool Count5/5

With 9 tools covering core task lifecycle operations (create, read, update, delete-like via cancel/reset), the count is well-scoped for a task management server.

Completeness4/5

The tool set covers CRUD and status transitions comprehensively. Minor gaps include no explicit delete tool and limited filtering (only TODO flag for listing), but core workflows are fully supported.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources