Skip to main content
Glama

List tasks

list_tasks
Read-onlyIdempotent

The tasks of the workspace (Design, Development…), by name. To track time, use the project_task_id of a project of list_projects, not a task id.

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
statusNoFor an admin and the owner; another role reads the active records that take its time

Output Schema

NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety and determinism profile is fully covered structurally. The description adds only the workspace scope and the 'by name' framing, saying nothing about ordering, filtering behavior, or the counting/tracking caveat beyond the id warning. With annotations carrying the load, this is adequate but thin.

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

Conciseness3/5

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

It is short and front-loads the resource, which is good, but the second sentence is a compressed, easily misread aside about project_task_id that reads as a non-sequitur in a listing tool's description. The backticked identifier and the dangling 'of a project of list_projects' phrasing hurt clarity more than the brevity helps.

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 one-optional-parameter read-only list tool with full annotation coverage and an output schema, the description supplies the essential scope cue and does not need to explain return values. The main residual gap is what a 'task' contains versus a project task, but the output schema and the id warning cover enough for correct invocation.

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% and the single status parameter has an enum plus its own description, so the schema does the work. The description adds no meaning about the status filter (active/archived/all) and its only identifier discussion concerns project_task_id, which is not a parameter of this tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

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

The description is a noun phrase ('The tasks of the workspace (Design, Development…), by name') rather than an explicit verb+resource statement, so the listing action is only implied by the tool name and title. It does convey the scope (workspace-level task names) but offers no differentiation from get_task, which is the most likely sibling to confuse it with.

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

Usage Guidelines3/5

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

One routing hint is given: for time tracking, use the project_task_id from a project obtained via list_projects rather than a task id. That is useful context but it addresses a downstream concern (time entry creation) rather than saying when to call list_tasks instead of get_task or how it relates to list_time_entries.

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.

Resources