Damper

List Tasks

list_tasks

Read-onlyIdempotent

Get roadmap tasks. Returns backlog/planned/in-progress by default. Search by title, description, plan, user story, or exact label, and filter by type, quarter, etc. Use query before paginating when checking whether a matching task already exists.

Returns up to 50 tasks by default. Response includes total count. Tasks with incomplete blockers are excluded automatically. Task summaries include available dates such as createdAt, updatedAt, startDate, and dueDate. If total > returned tasks, paginate with offset (e.g. offset=50 for page 2).

Recommended: Call get_project_context before starting work to understand codebase patterns.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

Name	Required	Description
`sort`	No	Sort order: importance (priority+votes, default), newest, or votes
`type`	No	Filter by task type
`limit`	No	Max tasks to return (default: 50)
`query`	No	Search task title, description, implementation plan, user stories, or an exact label
`offset`	No	Skip first N tasks for pagination (default: 0)
`status`	No
`quarter`	No	Filter by quarter (e.g., "Q1 2025") or "none" for unscheduled
`projectId`	Yes	Project ID. Use list_projects to find available project IDs.
`hasSelfAssessment`	No	Filter to tasks that have or do not have a submitted structured self-assessment

Output Schema

Name	Required	Description	Default
`tasks`	Yes
`total`	Yes
`project`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Annotations already cover readOnly/idempotent/non-destructive safety, and the description adds substantial extra context: default status filter, 50-item default limit, automatic exclusion of blocked tasks, total count, and pagination semantics via offset. Rich behavioral disclosure beyond annotations.

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?

Front-loads purpose and defaults, then filtering and pagination detail with a clearly separated recommendation. Efficient overall, though the trailing 'Recommended' line is somewhat ancillary.

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?

An output schema exists so return details needn't be described, yet the description still usefully notes total count, available date fields, and blocker exclusion. Complete enough for a filtered-list tool with rich schema.

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

Parameters4/5

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

Schema coverage is 89% so the schema does most of the work, but the description adds meaning: default status set, query's multi-field search behavior, and pagination via offset (offset=50 for page 2). Slight added value over schema baseline.

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+resource ('Get roadmap tasks') and clarifies default scope (backlog/planned/in-progress). Clear what it returns, though it doesn't explicitly name the sibling get_task to distinguish single-task retrieval.

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 context: 'Use query before paginating when checking whether a matching task already exists' and recommends get_project_context before starting work. Lacks explicit exclusions versus get_task, but the usage context is well specified.

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

All Damper tools Inspect

Try in Browser

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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?