Rillsoft Project MCP server

Official

by rillsoft

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

Update RIS document

rillsoft_document_ris_update

Destructive

Update a document's description, DMS folder, or content in Rillsoft Project's document management. Requires modify role; changes apply immediately.

Instructions

Changes the description, the DMS folder and/or the content of one document in the document management of the Rillsoft Integration Server - editing the description in the list, dragging it into a folder and the 'Upload' button of the documents page. At least one of description, folderId and path is required; the element the document hangs on cannot be changed (delete and attach again). Replacing the content with path is destructive: the stored file is overwritten and its name follows the new file. Takes effect on the server at once - no undo step, the project itself is not marked as changed. Without a path and without a difference nothing is sent. Runs with the login of the desktop session; needs the modify role.

Input Schema

TableJSON Schema

Name	Required	Description
`path`	No	absolute path of a local file whose content replaces the stored file; the document takes that file's name
`folderId`	No	id of the DMS folder to move the document into
`documentId`	Yes	id of the document, from rillsoft_document_ris_list
`description`	No	new description

Output Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	file name of the document
`note`	No	hints of the product path; missing when there were none
`uuid`	Yes	UUID of the element the document hangs on - a task, a subproject or the project itself
`fileSize`	Yes	size of the stored file in bytes
`folderId`	Yes	id of the DMS folder the document lies in
`createdAt`	Yes	time the document was stored, DD.MM.YYYY hh:mm; empty when the server reports none
`projectId`	Yes	id of the project the document belongs to
`documentId`	Yes	id of the document on the server; what _get, _update and _delete take
`folderPath`	Yes	names of the DMS folders from the root, joined by ' / '; empty when the folder is unknown to the tree
`description`	Yes	description; empty when none is set
`elementName`	Yes	name of that element
`createdUserName`	Yes	user who stored it; empty when the server reports none

Schema Changelog

Changes observed during successful MCP inspections.

First observedv10.0.626Oct 17, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations (destructiveHint=true, idempotentHint=false): it explains that path replacement overwrites the stored file and renames the document to the new file's name, that changes apply server-side immediately with no undo, that the project is not marked as changed, that it runs under the desktop session login, and that the modify role is required. This is exactly the extra behavioral context the annotations cannot convey.

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?

Front-loaded with the core action and the required-parameter constraint, and every clause carries real information (destructiveness, no undo, role requirement). It is dense and somewhat run-on, and the UI-action mapping (dragging, 'Upload' button) is slightly verbose, but nothing is filler.

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?

An output schema exists, so return values need not be described. Combined with the schema, the description covers auth requirements, side effects (overwrite/no undo/rename), the no-op condition, and the immovable-parent constraint, leaving no material gap for correct invocation.

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 per-field meanings are already documented (baseline 3). The description adds cross-parameter semantics the schema cannot express: the at-least-one-of constraint across description/folderId/path, and the consequence that replacing content via path also renames the document.

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 ('Changes') and the exact resources touched (description, DMS folder, and/or document content) within the Rillsoft Integration Server document management. It maps the operation to concrete UI actions (edit in list, drag into folder, Upload button), which distinguishes it from rillsoft_document_ris_create/delete/get without opening a 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?

Explicitly states the precondition that at least one of description, folderId, or path is required, and rules out changing the parent element ('cannot be changed - delete and attach again'), plus the no-op case ('without a path and without a difference nothing is sent'). It does not name sibling tools as alternatives by name, but the when/when-not conditions are clear.

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

Deploy Server