Skip to main content
Glama
Sign In
Task Manager

Task Manager

by vshfrost
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_tasks

Read-only

Lists planner tasks with optional filters for status, project, priority, domain, and title/text query; hides completed tasks by default and returns concise rows for quick review.

Instructions

Список задач із planner (короткі рядки: id, статус, заголовок, пріоритет, дедлайн, проєкт). Без status задачі done не показуються (внизу — скільки приховано); status=done — лише вони. Фільтри опційні: status = backlog|todo|blockers|in_progress|in_review|testing|done; project = слаг проєкту або 'global'; priority = asap|high|low; domain = тег без '#'; query = підрядок у заголовку чи тексті. status=todo — у ручному порядку колонки To Do (зверху те, що брати першим), не за пріоритетом. limit — скільки задач показати (за замовч. 50). Повний текст і links — get_task(id).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
domainNo
statusNo
projectNo
priorityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real behavioral detail beyond that: done tasks are hidden by default with a count of how many were suppressed, and status=todo results follow the manual To Do column order (top = do first) rather than priority order. It does not describe pagination beyond the limit default.

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

Conciseness4/5

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

Information is front-loaded: return shape first, then default filtering behavior, then the filter vocabulary, then a pointer to get_task. Every sentence carries semantics, though the dense run of filter definitions could be broken into a short list for faster scanning.

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?

There is no output schema, and the description compensates by listing the fields each returned row contains and noting that suppressed done tasks are counted. Combined with the six-parameter filter vocabulary and the get_task escape hatch, nothing an agent needs to call this correctly is missing.

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 0% and none of the six parameters carry enums, so the description must carry the full burden — and it does: it enumerates all seven status values, the priority values asap|high|low, project as a slug or 'global', domain as a tag without '#', query as a substring of title or text, and limit's default of 50. This is meaning no schema field provides.

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?

Names a specific verb+resource (list tasks from planner) and immediately specifies the shape of each row (id, status, title, priority, deadline, project). It also names get_task as the tool for full text and links, so an agent can distinguish the two without opening any schema.

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

Usage Guidelines4/5

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

Gives concrete usage context: with no status filter, done tasks are omitted and only a hidden count is shown; status=done returns only done tasks. It explicitly routes the agent to get_task(id) when full text and links are needed. What is missing is any explicit statement of when this tool should not be used at all (e.g. for mutation or board views).

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