D-Tools MCP Server

create_task

Create tasks in D-Tools System Integrator by providing a name, with optional project, description, status, assignee, and due date.

Instructions

Create a new task in D-Tools SI. Requires a name; optionally accepts project, description, status, assignee, and due date.

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": {
      "task": "<task>"
    },
    "name": "create_task"
  }
}

Input Schema

Name	Required	Description	Default
`task`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 12, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states required and optional fields, but does not disclose side effects, permissions, id generation, or validation constraints. A creation tool should clarify such traits.

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?

The description is concise with two short sentences and no fluff. However, it could be slightly more structured by listing fields explicitly or adding a note about return value.

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

Completeness2/5

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

Given the nested object schema with 7 parameters, no output schema, and no annotations, the description is too minimal. It does not explain the return value, validation, or expected behavior, making it incomplete for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate. It lists optional fields including 'project' but the schema has 'projectId', causing inconsistency. It also misses the 'id' field. The description adds minimal meaning beyond the schema.

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 clearly states 'Create a new task in D-Tools SI,' which is a specific verb+resource. It differentiates from sibling tools like update_task or list_tasks by focusing on creation.

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 use when creating a task, but it does not explicitly state when not to use it or compare with alternatives like update_task. No exclusions are given.

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