Rillsoft Project MCP server

Official

Overview Schema Source Related Servers Discussions Admin

Attach RIS document

rillsoft_document_ris_create

Stores a local file as a new document in the Rillsoft Integration Server DMS, attaching it to a task by task UUID and DMS folder ID. Requires a saved project and DMS create permissions.

Instructions

Stores a local file as a new document in the document management of the Rillsoft Integration Server and hangs it on a task, a subproject or the project itself - the 'Add' button of the documents page. Today the server accepts documents on tasks only: a subproject or the project itself answers ris_not_found (the text says why), so give the uuid of a task. Takes effect on the server at once: no undo step, the project itself is not marked as changed, and rillsoft_history_undo does not take it back; rillsoft_document_ris_delete removes it. Requires the project to be stored on the server (rillsoft_project_ris_save_as first for a new one), the DMS license function and the create role; refused in an open portfolio, as in the documents dialog; the answer is the document as the server holds it afterwards.

Input Schema

TableJSON Schema

Name	Required	Description
`path`	Yes	absolute path of the local file to store; its file name becomes the document name
`uuid`	No	UUID of the task or subproject the document hangs on; missing = the project itself
`folderId`	Yes	id of the DMS folder the document goes into, from folders[] of rillsoft_document_ris_list
`description`	No	description stored with the document

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?

Annotations cover only the read/write/idempotency profile, but the description adds rich context the annotations cannot: immediate effect with no undo (history_undo does not take it back), the project is not marked as changed, refusal in an open portfolio, auth/license requirements, and that the response is the stored document.

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 purpose and key constraint are front-loaded and nearly every clause carries operational value (undo behavior, prerequisite tools, restrictions). It is, however, a dense run-on paragraph that could be structured with clearer breaks to improve parseability.

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?

For a mutation tool with an output schema and annotations present, the description covers prerequisites, side effects, restrictions, and return value, leaving nothing an agent would need in order to call it correctly.

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 all four parameters. The description reinforces usage (task uuid needed, folderId from rillsoft_document_ris_list) but adds no syntax or format detail beyond what the schema provides, matching the baseline for full coverage.

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: stores a local file as a new DMS document on the Rillsoft Integration Server and attaches it to a task/subproject/project, explicitly likening it to the 'Add' button. This clearly distinguishes it from siblings like rillsoft_document_ris_update and rillsoft_document_ris_delete.

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?

Gives explicit when-to-use conditions and constraints: documents are accepted on tasks only today, subproject/project answers ris_not_found, so pass a task uuid. It also points to rillsoft_document_ris_delete for removal and states prerequisites (project stored, DMS license, create role).

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

Deploy Server