Skip to main content
Glama
Sign In
SmartBear MCP server

SmartBear MCP server

Official
by SmartBear
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Contract Testing: Admin Remove Role from User

contract-testing_admin_remove_role_from_user
DestructiveIdempotent

Remove a single role from a specified user by providing user and role UUIDs to manage admin access assignments.

Instructions

Remove a single role from a user (admin).

Toolset: Admin

Parameters:

  • userId (string) required: UUID of the user

  • roleId (string) required: UUID of the role

Input Schema

NameRequiredDescriptionDefault
roleIdYesUUID of the role
userIdYesUUID of the user

Output Schema

NameRequiredDescriptionDefault
successYesThe operation completed; the API returns no body.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.43.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "success": {
+      "const": true,
+      "description": "The operation completed; the API returns no body.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success"
+  ],
+  "type": "object"
+}
  2. Addedv0.40.0
  3. Removedv0.34.0
  4. First observedv0.27.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false and openWorldHint=false, so the risk profile is covered by structured data. The description adds only the useful nuance that exactly one role is removed and that admin privileges are needed; it says nothing about failure behavior when the user lacks that role.

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?

One front-loaded sentence captures the action, and the parameter block is compact. The parameter list duplicates the input schema, which is minor waste rather than a structural flaw.

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?

For a two-parameter destructive mutation with full annotation coverage and an output schema, the essentials are present and return values need not be explained. Gaps remain around the admin authorization requirement, error behavior for unassigned roles, and routing against sibling role-management tools.

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 coverage is 100% and both properties already carry 'UUID of the user' / 'UUID of the role' descriptions. The description's parameter list restates those verbatim, adding no new meaning such as where the UUIDs come from or whether the role must already be assigned.

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?

States a specific verb and resource: 'Remove a single role from a user', with '(admin)' signaling the privileged toolset. The 'single role' wording distinguishes it from bulk-role operations such as set_user_roles, though it never names those siblings explicitly.

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?

There is no when-to-use guidance, no prerequisite statement beyond the parenthetical '(admin)', and no mention of alternatives. An agent must infer from the name alone whether to revoke one role here versus overwriting the full set via contract-testing_admin_set_user_roles.

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

Deploy Server

Other Tools