Skip to main content
Glama
Sign In
SmartBear MCP server

SmartBear MCP server

Official
by SmartBear
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Contract Testing: Admin Delete User

contract-testing_admin_delete_user
DestructiveIdempotent

Deletes an admin user account using its UUID so AI assistants can manage SmartBear contract-testing access and remove users who should no longer have it.

Instructions

Delete a user account (admin).

Toolset: Admin

Parameters:

  • userId (string) required: UUID of the user

Input Schema

NameRequiredDescriptionDefault
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

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description only adds the parenthetical '(admin)', hinting at admin-level privileges, but says nothing about cascading effects (team memberships, roles, API tokens, audit trail) or confirmation of permanent removal.

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?

The core sentence is short and front-loaded. The 'Toolset: Admin' and 'Parameters' markdown block duplicate metadata already in the annotations and schema, which is mild padding but not confusing.

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?

With one required parameter, full schema coverage, an output schema, and annotations declaring destructiveness and idempotency, the definition covers the mechanical minimum. It falls short on the consequences of deletion, which matter for an admin destructive action.

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 schema already documents userId as 'UUID of the user'; the description merely restates it verbatim, adding no format, source, or lookup guidance (e.g., use list_users to obtain the UUID). Baseline 3 applies when the schema carries the semantics.

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 ('Delete a user account') and tags its scope with '(admin)'. The name plus description make it clearly distinct from siblings like delete_role, delete_team, or remove_user_from_team, though the description itself does not name those alternatives.

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 when-to-use guidance is given: nothing about when to delete vs. remove a user from a team (contract-testing_admin_remove_user_from_team) or revoke roles instead of deleting. No prerequisites or irreversibility warning are stated despite it being a permanent destructive operation.

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