Skip to main content
Glama
rillsoft

Rillsoft Project MCP server

Official

Create task

rillsoft_task_create

Create a task in Rillsoft Project under a project or subproject with optional dates, notes, milestone, and duration; calendar-computed dates and the task UUID are returned.

Instructions

Creates a task (RP computes the dates through the calendar) and returns its UUID. Changing it afterwards goes through rillsoft_task_update, moving it in the structure through rillsoft_element_move, deleting it through rillsoft_task_delete. In a portfolio parentUuid names a project or a subproject inside it - nothing is created directly below the portfolio, as in the user interface. One undo step.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesname of the task
notesNonotes on the task
startNostart, DD.MM.YYYY hh:mm; defaults to the start of the parent
finishNofinish, DD.MM.YYYY hh:mm (durationHours is the alternative)
fixedTypeNotask type: duration, effort, duration_effort (defaults to the application default from the settings). It says which quantity RP holds fixed while computing: duration keeps the duration, effort keeps the effort, duration_effort keeps both. This matches the choice in the task dialog
milestoneNotrue = milestone (duration 0, date fixed)
parentUuidNoUUID of the project or subproject; empty = the main project
durationHoursNoduration in hours (finish is the alternative)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
wbsYesWBS code
nameYesname
uuidYesUUID of the element
startYesstart, DD.MM.YYYY hh:mm
finishYesfinish, DD.MM.YYYY hh:mm
numberYesnumber of the element; unique even for split tasks
milestoneYestrue = the task that was created is a milestone

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv10.0.626

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, so the mutation profile is known. The description adds genuine context beyond that: dates are computed by RP through the calendar rather than taken literally, and the operation consumes exactly one undo step. Missing only things like selection/visibility side effects on the newly created task.

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?

Three sentences: what it does and returns, then the sibling routing, then the parentUuid constraint. Front-loaded with the primary action and no filler; every sentence carries distinct information.

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

Completeness5/5

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

With an output schema present and 100% schema description coverage, the description only needs to carry behavioral and routing context — calendar-driven date computation, undo semantics, sibling routing, and the portfolio constraint all present. Nothing an agent needs to call this correctly is missing.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description earns extra by clarifying parentUuid semantics (it names a project or subproject within a portfolio, and never the portfolio itself), which goes beyond the schema's terse "UUID of the project or subproject; empty = the main project".

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?

States a specific verb+resource ("Creates a task") plus two concrete outcomes: RP computes dates through the calendar and a UUID is returned. It then names the sibling tools for the adjacent operations (task_update, element_move, task_delete), making it trivially distinguishable from them.

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

Usage Guidelines5/5

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

Explicitly routes the agent to alternatives for follow-up operations (changing, moving, deleting) and states a hard usage constraint for parentUuid: nothing can be created directly below the portfolio, unlike the UI. Both when-to-use and when-not are covered.

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