D-Tools MCP Server

list_tasks

List tasks from D-Tools SI with filters for project, search text, pagination, and deleted or imported status.

Instructions

List D-Tools SI tasks with optional filters for project association, search text, pagination, and deleted or imported status.

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

Name	Required	Description	Default
`pageSize`	No
`projectId`	No
`pageNumber`	No
`searchText`	No
`includeDeleted`	No
`includeImported`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 12, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are provided, so the description carries full burden. It states the tool lists tasks but does not disclose whether it is read-only, authentication needs, rate limits, or pagination defaults. Adequate but not detailed.

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?

The description is a single sentence of 18 words, front-loading the action and filters. Every phrase adds value, with no redundancy or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 6 parameters, no output schema, and no annotations, the description is somewhat complete but lacks return format details (e.g., returns list of task objects) and pagination behavior (defaults, max page size). Adequate for a simple list tool but could be more informative.

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 0%, so the description must add meaning. It maps filters to parameters (projectId, searchText, includeDeleted, includeImported, pageSize, pageNumber) but does not explain constraints, defaults, or search scope. Baseline 3 due to coverage gap.

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?

The description explicitly states the tool lists D-Tools SI tasks with optional filters, distinguishing it from sibling list tools for other entities like clients, projects, etc. It uses specific verb+resource and mentions filter categories.

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?

The description implies usage for listing tasks with filters, but does not provide guidance on when to use this tool versus alternatives like get_task for a single task or other list tools. No exclusions or context given.

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