action1-mcp-server

List the roles assigned to a user

action1_list_user_roles

Read-onlyIdempotent

Retrieve all roles assigned to a specific user by ID to review access and audit permissions.

Instructions

List the roles assigned to a user. Retrieves all roles assigned to a user specified by ID. Perm: manage_users.

Input Schema

Name	Required	Description
`from`	No	Provide the number of the first record to be returned.
`limit`	No	Set the maximum number of items to be returned (the page size).
`cursor`	No	next_cursor of the previous call; takes precedence over from.
`user_id`	Yes	Provide a specific user ID.
`verbose`	No	Skip per-item compactor.
`auto_paginate`	No	Walk pages until limit or the size budget; then continue with next_cursor.
`response_format`	No	Output format. Default markdown.

Output Schema

Name	Required	Description	Default
`note`	No
`count`	Yes
`items`	Yes
`total`	No
`has_more`	No
`next_cursor`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedv0.6.0Oct 26, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedInput schema / properties / auto_paginate / description

Previous value: -"Walk all pages."New value: +"Walk pages until limit or the size budget; then continue with next_cursor."

changedInput schema / properties / cursor / description

Previous value: -"Pagination cursor."New value: +"next_cursor of the previous call; takes precedence over from."

addedInput schema / properties / from / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / from / minimum
```
Added value: +0
```
addedInput schema / properties / limit / maximum
```
Added value: +50000
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```

changedInput schema / properties / limit / type

Previous value: -"number"New value: +"integer"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +{}
```

addedOutput schema / properties / items / items / properties

Added value: +{
+  "description": {},
+  "id": {},
+  "name": {},
+  "scoped_permissions": {},
+  "self": {},
+  "type": {},
+  "users": {}
+}

First observedv0.5.0Jun 27, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, so safety is covered. The description adds the required permission ('Perm: manage_users'), which is genuinely new authorization context not present in annotations or schema. It stops short of noting pagination or result-set behavior, though that is largely encoded in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

Front-loaded correctly with the action, but the second sentence ('Retrieves all roles assigned to a user specified by ID') largely restates the first sentence rather than adding information, which dilutes an otherwise three-sentence description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and the schema documents all parameters, so the description need not explain return values. Still, for a list tool among dense siblings it omits the one thing that isn't encoded elsewhere: how it differs from action1_list_role_users and what the permission requirement means for failure modes.

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 all seven parameters including from, limit, cursor, verbose, auto_paginate and response_format are already documented. The description only echoes the required user_id ('specified by ID') and adds nothing about pagination or format selection. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb+resource: 'List the roles assigned to a user', with the direction of the relationship (user -> roles) made explicit. That implicitly distinguishes it from the sibling action1_list_role_users, which goes role -> users, though it never names that alternative.

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

Usage Guidelines3/5

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

The required user_id establishes the scope, so an agent can infer when this applies. However, there is no explicit statement of when to use this over action1_list_role_users or action1_get_user, and no prerequisites or exclusions are given.

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

Deploy Server