Rillsoft Project MCP server

Official

by rillsoft

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

List RIS folders

rillsoft_folder_ris_list

Read-onlyIdempotent

Lists the project folder tree from the Rillsoft Integration Server with ID, path and depth per folder, so you get the folderId needed by save-as and other folder tools without nested-set arithmetic.

Instructions

Lists the project folder tree of the logged-in client on the Rillsoft Integration Server - the tree of the 'Open from database' dialog - with parentFolderId, path and depth per folder, so no nested-set arithmetic is needed; the folderId is what rillsoft_project_ris_save_as and the other folder tools take. Not the DMS folder tree of the documents (rillsoft_document_ris_list). Runs with the login of the desktop session. Read-only, no undo step.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`permission`	No	only folders the logged-in user holds this permission for; project_read is the default	project_read

Output Schema

TableJSON Schema

Name	Required	Description
`server`	Yes	URL of the Rillsoft Integration Server the desktop session is logged in to
`folders`	Yes	every folder the permission allows, in tree order (root first, children right after their parent)
`clientId`	Yes	id of the logged-in client; -1 while none is selected
`userName`	Yes	user name of the desktop session
`permission`	Yes	the permission the tree was filtered by

Schema Changelog

Changes observed during successful MCP inspections.

First observedv10.0.626Oct 17, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint, so safety is covered. The description still adds genuine context: it runs under the desktop session login, corresponds to a specific dialog, and restates that there is no undo step. It stops short of describing pagination or tree-size limits, so not a 5.

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 purpose, then exclusions, then auth/behavior — a sensible order with little waste. 'Read-only, no undo step' partially duplicates the annotations, which keeps it from being maximally tight.

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 it needn't explain return values, and it doesn't over-explain them. Purpose, routing to the correct sibling, the consuming tools, and the auth/session context are all present, leaving nothing an agent needs before calling.

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% and the single 'permission' enum is fully documented in the schema (default project_read, meaning of each value). The description says nothing further about the parameter, so the baseline 3 for schema-does-the-work applies.

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 ('Lists the project folder tree'), identifies the concrete UI surface ('the tree of the Open from database dialog'), and lists the returned fields (parentFolderId, path, depth). It also names the sibling it is NOT (rillsoft_document_ris_list) so the agent can distinguish it 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 Guidelines5/5

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

Provides an explicit exclusion ('Not the DMS folder tree of the documents (rillsoft_document_ris_list)') and states the downstream consumers of the output, naming rillsoft_project_ris_save_as and 'the other folder tools'. That covers both when to use it and where its output flows, which is exactly what routes an agent correctly.

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

Deploy Server