Skip to main content
Glama

tasks_list

Read-onlyIdempotent

Lists a project's tasks with optional status, plan, or single-task lookup, and shows gate details for tasks waiting on people.

Instructions

List a project's tasks, optionally filtered by status, newest first. A task that waits on people carries its gate (who, what, and whether it is still open), and a task of kind gate says so. By default plan-step tasks are excluded; pass plan= to list that plan's steps instead. Pass id= to load a single task by its globally-unique id (a direct lookup that ignores project/status/plan and needs no session scope).

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": "tasks_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoload exactly one task by its globally-unique id; when set, project/status/plan are ignored and the response's tasks array holds just that task
planNooptional plan slug: list that plan's step tasks instead of the default (non-plan) tasks
statusNooptional status filter
projectNoproject slug; defaults to the bound session's project
sessionNothe session to act as: the name session_start returned, the cc/<id> or cx/<id> on your briefing's 'Seam session' line, or a session ULID. It scopes and credits this call. Defaults to this connection's session; pass it on every call when session_start reports the connection as stateless

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.4
    • addedInput schema / properties / session
      Added value: +{
      +  "description": "the session to act as: the name session_start returned, the cc/<id> or cx/<id> on your briefing's 'Seam session' line, or a session ULID. It scopes and credits this call. Defaults to this connection's session; pass it on every call when session_start reports the connection as stateless",
      +  "type": "string"
      +}
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare the safe-read profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the description adds genuinely new behavioral context: default exclusion of plan-step tasks, newest-first ordering, the shape of task payloads (gate carries who/what/open state, gate kind self-declares), and that the id path ignores project/status/plan and needs no session scope.

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?

Three sentences, front-loaded with the core list behavior before the two special modes; no filler. The gate clause is dense but informative and belongs, since no output schema documents the return shape.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description usefully characterizes what comes back (tasks array, gate payload, gate kind). It covers defaults, filters, and override interactions; the only gap is nothing said about result size, ordering guarantees beyond 'newest first', or pagination/limits for large projects.

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 coverage is 100%, so the schema already documents id, plan, status, project and session semantics. The description largely restates the schema's id/plan behavior; its only real addition is that a direct id lookup 'needs no session scope', which is operationally useful but thin. Baseline 3 fits 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List a project's tasks') plus filter scope and ordering ('newest first'), and disambiguates its own modes: default listing, plan-step listing, and single-task lookup by id. It never names a sibling tool (e.g. tasks_ready), so an agent must infer how this differs from other task readers.

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 explicit conditional guidance for the two non-obvious paths: 'By default plan-step tasks are excluded; pass plan=<slug> to list that plan's steps instead' and 'Pass id=<task id> to load a single task'. What is missing is guidance about when to prefer this tool over alternatives such as tasks_ready or tasks_claim.

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