Rillsoft Project MCP server

Official

by rillsoft

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

Select RIS resource pool

rillsoft_resource_pool_ris_select

Idempotent

Switches the global resource pool to a selected RIS client's pool and sets that client as the session login. Requires a new unmodified project and no open work unit; create the project first.

Instructions

Switches the global resource pool to the pool of a client on the Rillsoft Integration Server and makes that client the logged-in client of the session (clientId of the other RIS tools). Possible only on a new, unmodified project and without an open unit of work, so call rillsoft_project_create first. A pool file is selected through rillsoft_resource_pool_file_select instead. Runs with the login of the desktop session and never asks for credentials. No undo step; the setting holds application-wide and survives a restart.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`clientId`	Yes	id of the client on the server whose resource pool becomes the global pool, from rillsoft_resource_pool_ris_list

Output Schema

TableJSON Schema

Name	Required	Description
`path`	No	path of the pool file; only with source file
`roles`	Yes	number of qualifications
`teams`	Yes	number of teams
`client`	No	tenant; only with source ris
`source`	Yes	origin of the resource pool
`workUnit`	Yes	state of the unit of work on the pool
`calendars`	Yes	number of calendars
`employees`	Yes	number of people
`versionId`	Yes	id of the pool version that was loaded from the server

Schema Changelog

Changes observed during successful MCP inspections.

First observedv10.0.626Oct 17, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the annotations (which cover idempotency and non-destructiveness), the description discloses the session side effect (the client becomes the logged-in client used as clientId by other RIS tools), auth behavior (desktop session login, never prompts for credentials), persistence (application-wide, survives restart), and irreversibility (no undo step). These are exactly the traits 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the core action, then layers preconditions, alternative, auth, and persistence in tight sentences. Every sentence carries a distinct constraint or consequence with no 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?

Output schema exists so return values need not be described, and the description fully covers preconditions, side effects, auth, and persistence for a stateful global-setting tool. Nothing an agent needs to call it correctly is missing.

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 100%, so baseline is 3, but the description adds meaning the schema does not: the selected clientId also becomes the session's logged-in client referenced by the other RIS tools, not just the pool source. That cross-tool consequence is genuinely useful beyond the property description.

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 ('Switches the global resource pool to the pool of a client on the RIS') and explicitly separates itself from the similarly named sibling rillsoft_resource_pool_file_select. An agent can distinguish it from the file-select variant without opening either 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?

Gives explicit preconditions ('only on a new, unmodified project and without an open unit of work'), a prerequisite action ('call rillsoft_project_create first'), and the alternative to use otherwise ('rillsoft_resource_pool_file_select'). This is full when/when-not/alternative guidance.

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

Deploy Server