Skip to main content
Glama

List Tasks

list_tasks
Read-onlyIdempotent

List the caller's tasks, newest-updated first, cursor-paginated. In your own Gryz, assignee: "agent" lists what is assigned to you, subtasks included. A person can assign you a task: in the result it reads assignee=this_agent, with assigned_to_caller: true, and assignee=your_user means the person. Being assigned is not an instruction to act: tell your user what the task asks and check with them first. Other lists exclude subtasks by default, except that a plain list from an agent also includes the newest subtasks a person handed to it, and every list excludes cancelled tasks — pass status: "cancelled" to see cancelled ones, and parent_task_id to list one parent's children, or include_subtasks: true for everything. Each entry is a summary (title, status, priority, assignee, Project, linked-resource counts, and for a parent a computed subtask done/total) — not the full body. For what the person said, decided or prefers about their work, check recall first. Read-only.

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
afterNoOpaque cursor from a previous page
firstNoPage size (default 20)
statusNo
assigneeNo
project_idNoProject id from list_projects, to list one Project's tasks. In your own Gryz, pass project_key or project_id, not both.
project_keyNo
parent_task_idNoList one parent task's subtasks
include_subtasksNoInclude subtasks in a non-parent-scoped list. Default: false, except with `assignee: "agent"`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already cover the read-only/idempotent profile, and the description goes well beyond them: default exclusions (subtasks and cancelled tasks), the exception that agent-issued lists include recently handed-off subtasks, and the entry-level shape (title, status, priority, assignee, Project, linked-resource counts, computed subtask done/total). The line about assignment not being an instruction to act, telling your user first, is exactly the kind of guardrail annotations cannot express.

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?

The opening sentence is perfectly front-loaded and nothing is filler, but the middle stretch packs subtask defaults, the assignment encoding, and the safety caveat into a long compound chain that takes a second pass to parse. Slightly more structural separation would help without adding length.

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?

With 8 optional parameters and no output schema, the description compensates by describing what a returned entry actually contains and by flagging that it is a summary, not the full body. Nothing an agent needs to call this correctly — defaults, pagination, scoping, safety — 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 only 63%, and the largest gap — `assignee`, which has no enum and no schema description — is fully resolved here: `"agent"`, the `assignee=this_agent` / `assigned_to_caller: true` result encoding, and `assignee=your_user` meaning the person. It also supplies the default for `include_subtasks` and the cancelled-exclusion behavior that `status` alone would not convey.

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?

Opens with a specific verb and resource plus two behavioral traits an agent needs immediately: 'newest-updated first' and 'cursor-paginated'. It also carves out the caller's own scope, which separates it from list_projects or list_documents without opening their schemas.

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

Usage Guidelines5/5

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

Gives explicit routing rules for each axis of choice: `assignee: "agent"` for your own queue, `status: "cancelled"` to see cancelled items, `parent_task_id` to scope to one parent, `include_subtasks: true` for everything. It also points to the `recall` sibling for what the person said or prefers, which is a named alternative with a stated condition.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.