Skip to main content
Glama
Sign In
projectlibre-mcp

projectlibre-mcp

by augmdc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_tasks

List tasks from a .pod project file, showing hierarchy, dates, and predecessors. Filter by completion status or date range.

Instructions

List tasks in a .pod project with hierarchy, dates, and predecessors.

Args: path: Absolute path to the .pod file. incomplete_only: Drop summary rows and tasks at 100%. start_after: Keep tasks starting on/after this date (YYYY-MM-DD). finish_before: Keep tasks finishing on/before this date (YYYY-MM-DD).

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": {
      "path": "<path>"
    },
    "name": "list_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
start_afterNo
finish_beforeNo
incomplete_onlyNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It explains argument effects (e.g., incomplete_only drops rows) but does not disclose side effects, authentication needs, or read-only nature. Output schema compensates but description could be more explicit.

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?

Description is concise: one-sentence purpose followed by clear argument list. No fluff or repetition, every sentence adds value.

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?

Given output schema, description doesn't need to detail return values. It covers all parameters and hints at output content. Missing explicit mention of read-only or performance characteristics, but still adequately complete for a listing tool.

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 description coverage is 0%, but description provides detailed docstring for all 4 parameters (path, incomplete_only, start_after, finish_before), explaining their purpose and formats clearly.

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?

Description clearly states verb 'List' and resource 'tasks in a .pod project', and specifies included data (hierarchy, dates, predecessors). Distinguished from siblings like list_projects and get_project_summary.

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?

Purpose implies usage for listing tasks, but description lacks explicit when-to-use or when-not-to-use guidance relative to siblings. No exclusion criteria or alternative tool mentions.

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