Skip to main content
Glama
CronusL-1141

AI Team OS

by CronusL-1141
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

task_list_project

Get the task wall — project-scoped by default, team-scoped on request.

Instructions

Get the task wall — project-scoped by default, team-scoped on request.

Pass team_id to narrow the wall to one team; leave it empty to get every team under the project plus the project-level tasks that belong to no team.

Project scope leads with digest: the whole wall in one text block (open counts by status and horizon, 7-day trend, stale and dormant counts, the 5 most recent actions, the top 5 pending, the first mid and long pending task). It is the same block the session briefing shows; read it first, the rows below are one page.

Default response is a COMPACT projection (marked by view="compact" + hint — it is a trimmed view, NOT missing fields): each task row keeps id/title/priority/status/score/assigned_to/tags + 80-char desc excerpt (plus result/depends_on/subtask_count when present). Full details of a single task: task_status(task_id) / task_memo_read(task_id).

Input Schema

NameRequiredDescriptionDefault
limitNoMax number of pending tasks to return (default 50; project scope only). Running, blocked and failed tasks always come back in full; not_shown counts the pending tasks left off the page.
fieldsNo"compact" (default, trimmed projection) / "all" (full rows)compact
offsetNoPagination offset for pending tasks (default 0; project scope only)
statusNoFilter by status: pending/running/blocked/failed/completed (default: every status except completed; project scope only). status="completed" returns rows only together with include_completed=True; on its own it yields an empty wall.
horizonNoFilter by time horizon: "short" / "mid" / "long" (optional)
team_idNoTeam UUID - narrows the wall to one team (optional). Names are not resolved here and return an empty wall; get the id from team_list
priorityNoFilter by priority: "critical" / "high" / "medium" / "low" (optional; comma-separated accepted for multiple)
project_idNoProject ID (optional, auto-uses active project if empty; ignored when team_id is given)
include_completedNoInclude completed tasks (default False; project scope only)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.15.2
    • changedInput schema / properties / team_id / description
      Previous value: -"Team ID or name — narrows the wall to one team (optional)"New value: +"Team UUID - narrows the wall to one team (optional). Names\nare not resolved here and return an empty wall; get the id\nfrom team_list"
  2. Changed3 schema fields changedv1.15.0
    • changedInput schema / properties / limit / description
      Previous value: -"Max number of active tasks to return (default 50; project scope only)"New value: +"Max number of pending tasks to return (default 50; project scope\nonly). Running, blocked and failed tasks always come back in full;\nnot_shown counts the pending tasks left off the page."
    • changedInput schema / properties / offset / description
      Previous value: -"Pagination offset for active tasks (default 0; project scope only)"New value: +"Pagination offset for pending tasks (default 0; project scope only)"
    • changedInput schema / properties / status / description
      Previous value: -"Filter by status: pending/running/blocked/completed\n(default all active; project scope only)"New value: +"Filter by status: pending/running/blocked/failed/completed\n(default: every status except completed; project scope only).\nstatus=\"completed\" returns rows only together with\ninclude_completed=True; on its own it yields an empty wall."
  3. Changed8 schema fields changedv1.11.2
    • addedInput schema / properties / fields
      Added value: +{
+  "default": "compact",
+  "description": "\"compact\" (default, trimmed projection) / \"all\" (full rows)",
+  "type": "string"
+}
    • changedInput schema / properties / include_completed / description
      Previous value: -"Include completed tasks in response (default False)"New value: +"Include completed tasks (default False; project scope only)"
    • changedInput schema / properties / limit / description
      Previous value: -"Max number of active tasks to return (default 50)"New value: +"Max number of active tasks to return (default 50; project scope only)"
    • changedInput schema / properties / offset / description
      Previous value: -"Pagination offset for active tasks (default 0)"New value: +"Pagination offset for active tasks (default 0; project scope only)"
    • changedInput schema / properties / priority / description
      Previous value: -"Filter by priority: \"critical\" / \"high\" / \"medium\" / \"low\" (optional)"New value: +"Filter by priority: \"critical\" / \"high\" / \"medium\" / \"low\"\n(optional; comma-separated accepted for multiple)"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project ID (optional, auto-uses active project if empty)"New value: +"Project ID (optional, auto-uses active project if empty;\nignored when team_id is given)"
    • changedInput schema / properties / status / description
      Previous value: -"Filter by status: pending/running/blocked/completed (default all active)"New value: +"Filter by status: pending/running/blocked/completed\n(default all active; project scope only)"
    • addedInput schema / properties / team_id
      Added value: +{
+  "default": "",
+  "description": "Team ID or name — narrows the wall to one team (optional)",
+  "type": "string"
+}
  4. First observedv1.9.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full behavioral burden and does well: it discloses the compact projection behavior (a trimmed view, NOT missing fields), the digest block semantics, and staleness/dormancy counts. It does not cover auth requirements or rate limits, but for a read-oriented list tool the disclosure is above average.

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?

Well front-loaded with scope first, then digest, then the compact-projection caveat. The prose is dense but each paragraph earns its place; the digest description is somewhat long but justified given it is the primary consumption path.

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?

An output schema exists so return values need not be explained, and the description nonetheless explains the key output shape (digest + compact rows). Combined with 100% schema coverage and nine parameters, an agent has everything needed to call it correctly.

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

Parameters3/5

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

Schema description coverage is 100%, so parameters are already thoroughly documented in the schema (including scope-only caveats). The description adds the team_id-scoping concept and compact-view rationale but no syntax beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb+resource ('Get the task wall') and immediately differentiates scope: project-scoped by default, team-scoped on request. The digest explanation and the pointer to task_status/task_memo_read for single-task reads clearly distinguish it from the many sibling task tools.

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?

Explicitly says to read the digest first before the rows, and names task_status(task_id)/task_memo_read(task_id) for full single-task detail. It also explains the team_id/project_id interaction. It lacks an explicit 'when NOT to use' against siblings like briefing_list or project_summary, keeping it just short of a 5.

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