Skip to main content
Glama
rillsoft

Rillsoft Project MCP server

Official

Assign resources automatically

rillsoft_task_resource_assignment_fill

Bulk-assign employees or machines to tasks based on role requirements. Skips tasks with conflicts or closed balance and returns assignments made plus skipped causes.

Instructions

The 'Assign staff' respectively 'Assign machine park' wizard: fills many tasks at once out of their role assignments. One call is exactly one undo step, labelled like the menu entry. An assignment is made only where the task carries the matching role, the resource is not on it yet, it is not already involved through another role, and the balance of that role is still open. The result gives the assignments made per task plus skipped[] with the cause. Only at progress 0 %.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoautomatic (the default) applies the rule behind the 'Select all' button (balance still open, no schedule conflict, and for people 100 % availability on top); selection takes only the pairs given in assignmentsautomatic
typeNoresource type; employee by default. Here resource covers exactly these two - an assistant works on concrete people and machines. The other four resource types (role, team, material, machine_role) are read and written through rillsoft_resource_usage_list and rillsoft_resource_usage_setemployee
taskUuidsNoUUIDs of the tasks; empty means every eligible task of the visible project or subproject, just like the menu entry
assignmentsNoonly with mode selection: an array of { taskUuid, resourceId }
resourceIdsNopreselection like the first wizard page; empty means every resource whose role the tasks call for

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYesoperating mode chosen
typeYesresource type
tasksYesthe tasks that were changed
skippedYesskipped tasks with the cause
assignedYesnumber of assignments made

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv10.0.626

TDQS

A4.3/5.0
Behavior5/5

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

Adds substantial behavior beyond annotations (which only say non-read-only, non-idempotent, non-destructive): each call is exactly one undo step, the precise conditions under which an assignment is made, and the 0% progress constraint. It also describes the failure reporting (skipped[] with cause).

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?

Dense but front-loaded: the batch-wizard purpose leads, followed by undo semantics and the assignment conditions. Sentences are telegram-style and a bit run-on in the rules list, but nearly every clause carries actionable 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 non-idempotent mutation with an available output schema, the description covers preconditions, undo behavior, and result shape (per-task assignments plus skipped[]). It is nearly complete; the only minor gap is not explicitly pointing to sibling tools for the non-zero-progress case.

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%, so the schema already documents mode, type, taskUuids, assignments, and resourceIds. The description adds no syntax or format detail for these parameters beyond what the schema provides, making the baseline 3 appropriate.

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 and resource with scope: it 'fills many tasks at once out of their role assignments,' framing it as a batch wizard. This distinguishes it from single-assignment siblings like rillsoft_task_employee_assignment_set and rillsoft_task_role_assignment_set. An agent can tell it apart without opening the schema.

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

Usage Guidelines4/5

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

Gives a clear precondition ('Only at progress 0 %') and frames usage via the 'Assign staff'/'Assign machine park' wizard and the 'Select all' menu equivalent. It does not explicitly name alternative tools for assigning resources when this precondition fails, so it stops short of full alternative routing.

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