iSuite Operations MCP Server

list_roles

Retrieve a complete list of all roles defined in iSuite, optionally with full permission details for each role.

Instructions

List all available roles defined in iSuite.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_roles"
  }
}

Input Schema

Name	Required	Description	Default
`includePermissions`	No	Include the full permission list for each role (default false).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 13, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The description implies a read-only, non-destructive operation by using 'List'. With no annotations provided, the description covers the basic behavioral trait. However, it does not disclose potential pagination, performance characteristics, or any limits on the number of roles returned.

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?

The description is a single, clear sentence with no extraneous information. It is appropriately front-loaded and earns its place.

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?

Given the tool's simplicity (one optional boolean param, no output schema), the description is mostly complete. It lacks details on the return structure or role representation, but for a list tool this is acceptable.

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?

The input schema has 100% coverage with its single param described. The tool description adds no additional semantics beyond the schema's own description of 'includePermissions'. Baseline 3 applies as schema does the work.

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?

The description clearly states the verb 'List' and the resource 'all available roles defined in iSuite'. It effectively distinguishes from sibling tools like 'get_role' (single role) and 'list_role_members' (membership list), making the tool's purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. For example, it does not mention that this lists all roles without filtering, unlike 'get_user_roles' which lists roles for a specific user. Users must infer context from the name alone.

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