Skip to main content
Glama
Sign In
project-manager

project-manager

by charlesribeiro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_tasks

List project tasks with optional filters for status and priority to inspect, search, or summarize existing work.

Instructions

List project tasks, optionally filtering by status and/or priority. Use this when the user wants to inspect, search, or summarize existing tasks.

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
statusNoOptional task status filter
priorityNoOptional task priority filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so description must carry the burden. It implies read-only behavior by saying 'list' and 'inspect' but doesn't explicitly state that no modifications occur, nor does it describe output format or pagination. The description is adequate but not rich on behavior.

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

Conciseness5/5

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

Two sentences with no fluff. The core purpose and usage context are front-loaded, and it delivers all necessary information efficiently.

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?

For a simple list tool with two optional enum parameters and full schema coverage, the description is nearly complete. It could mention output format or that no task creation occurs, but the tool's simplicity makes the current description sufficient.

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 both parameters are already documented in the schema. The description's mention of 'optionally filtering' adds minimal extra meaning beyond the schema's 'Optional' descriptions. Baseline 3 is appropriate.

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?

Clearly states it lists project tasks with optional filtering by status and priority, distinguishing it from create/update siblings. The verb 'list' plus resource 'tasks' is specific and unambiguous.

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 states when to use: when the user wants to inspect, search, or summarize existing tasks. It does not explicitly mention alternatives (create_task/update_task) or when not to use, but the context is clear enough for an agent to select this tool for read-only queries.

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