Skip to main content
Glama
Local Development MCP Server

Local Development MCP Server

by lreb

list-tasks

Retrieve all tasks, optionally filtered by status, and sort them by priority and creation date to support task tracking.

Instructions

List all tasks, optionally filtered by status. Sorted by priority then creation date.

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
statusNoFilter by status (default: all)all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add real behavior: the operation is a read ("List") and results are sorted by priority then creation date. It omits other behavioral traits an agent would want, such as pagination, result limits, or what fields each task contains.

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?

Two compact sentences with the action front-loaded and the ordering detail second; nothing is wasted. It is on the terse side, but every clause carries information.

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 zero-required-parameter read tool with complete schema coverage and no output schema, this is close to sufficient: the agent knows what it gets and how it is ordered. The main gap is any indication of volume or return shape for a potentially large list.

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 description coverage is 100% and the enum values are fully documented in the schema, so the baseline is 3. The description's mention of status filtering restates the schema rather than adding meaning such as how "all" differs from omitting the parameter.

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 all tasks") plus the result ordering, so the agent knows exactly what it retrieves. It does not distinguish itself from the sibling search-tasks or tasks-completed-this-week, so an agent must infer which listing tool is appropriate.

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?

"optionally filtered by status" implies the intended use (browse tasks, narrow by status) but gives no explicit when-to-use versus search-tasks or when-not, and no prerequisite context. Usage is implied rather than directed.

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