Skip to main content
Glama
rillsoft

Rillsoft Project MCP server

Official

Create master data record

rillsoft_resource_pool_resource_create

Creates a single resource pool element (role, team, employee, etc.) within an open edit session. Nothing is stored until the edit is saved.

Instructions

Creates a single element in the resource pool. Inside an open unit of work only (rillsoft_resource_pool_edit_open); nothing is stored before rillsoft_resource_pool_edit_save. The group is picked through 'group' and created where it does not exist yet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYescatalog the object comes from
fieldsNofields of the new element. Permitted, depending on type: group, name, firstName, lastName, code, rank, email, calendarId, metric, teamId, roleId, machineRoleId, productivity, capacityType, capacity, employedFrom, employedTo, cost, costChange, notes, with employee and team additionally shiftCycles, and with project_customer additionally url, street, postalCode, city, region, country, contactPerson, phone. shiftCycles is the shift calendar as a list of { from, to, calendarId } (dates DD.MM.YYYY, to may be left out for a single day): in each period the named calendar applies instead of the assigned one. The periods must not overlap, and every calendarId has to exist in the pool. Read it back through rillsoft_resource_pool_resource_get

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNointernal id of the element
codeNocode of the element; missing when none is set
nameNoname of the element
typeYescatalog of the element
groupNoname of the group; missing for people and without a group name
outcomeYeswhat the call did

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv10.0.626

TDQS

A4/5.0
Behavior4/5

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

Annotations only cover the safety profile (not read-only, not destructive, not idempotent, not open-world). The description adds real behavior beyond that: the create is staged inside an edit session and discarded unless save is called, and a missing group is auto-created as a side effect. Error behavior if no edit session is open is left unstated.

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?

Three sentences, purpose front-loaded, each carrying distinct information (what it creates, the edit-session prerequisite, the group side effect). Slightly awkward phrasing in 'The group is picked through group' but nothing wasted.

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?

An output schema exists, so return values need not be described. The transactional prerequisite and the group side effect are covered; the multi-catalog 'type' dimension is left entirely to the schema, which is acceptable given its oneOf structure.

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 coverage is nominally 100%, but the field-level descriptions are placeholders like 'value of code', so the baseline is 3. The description earns a bump by explaining the 'group' parameter's semantics: it selects the group and creates it when it does not yet exist.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Creates a single element in the resource pool.' It is distinguishable from the sibling rillsoft_resource_pool_resource_update/delete/get by the create verb, though it never names those siblings explicitly.

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 hard prerequisite: it must run 'Inside an open unit of work only (rillsoft_resource_pool_edit_open)' and nothing persists until rillsoft_resource_pool_edit_save. That is strong when-to-use context, but there is no guidance on when to prefer this over resource_update for existing entries.

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