contract-testing_admin_reset_rolesResets all roles to factory defaults, restoring the default admin role configuration for SmartBear contract testing administration.
Reset all roles to their factory defaults (admin).
Toolset: Admin
Parameters: None
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| _links | No | ||
| _embedded | No |
Changes observed during successful MCP inspections.
v0.43.0Output schema / (root)Previous value: -nullNew value: +{
+ "$defs": {
+ "Action": {
+ "additionalProperties": {},
+ "properties": {
+ "href": {
+ "type": "string"
+ },
+ "method": {
+ "type": "string"
+ },
+ "name": {
+ "type": "string"
+ },
+ "title": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "EmbeddedLink": {
+ "additionalProperties": {},
+ "properties": {
+ "href": {
+ "type": "string"
+ },
+ "name": {
+ "type": "string"
+ },
+ "templated": {
+ "type": "boolean"
+ },
+ "title": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "Permission": {
+ "additionalProperties": {},
+ "properties": {
+ "description": {
+ "type": "string"
+ },
+ "group": {
+ "type": "string"
+ },
+ "label": {
+ "type": "string"
+ },
+ "scope": {
+ "type": "string"
+ },
+ "uuid": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "Role": {
+ "additionalProperties": {},
+ "properties": {
+ "_actions": {
+ "items": {
+ "$ref": "#/$defs/Action"
+ },
+ "type": "array"
+ },
+ "_links": {
+ "additionalProperties": {},
+ "properties": {
+ "self": {
+ "$ref": "#/$defs/EmbeddedLink"
+ }
+ },
+ "type": "object"
+ },
+ "created": {
+ "type": "string"
+ },
+ "createdAt": {
+ "type": "string"
+ },
+ "description": {
+ "type": "string"
+ },
+ "name": {
+ "type": "string"
+ },
+ "permissions": {
+ "items": {
+ "$ref": "#/$defs/Permission"
+ },
+ "type": "array"
+ },
+ "systemDefined": {
+ "type": "boolean"
+ },
+ "updatedAt": {
+ "type": "string"
+ },
+ "uuid": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ }
+ },
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
+ "additionalProperties": {},
+ "properties": {
+ "_embedded": {
+ "additionalProperties": {},
+ "properties": {
+ "roles": {
+ "items": {
+ "$ref": "#/$defs/Role"
+ },
+ "type": "array"
+ }
+ },
+ "type": "object"
+ },
+ "_links": {
+ "additionalProperties": {},
+ "properties": {
+ "pf:reset": {
+ "$ref": "#/$defs/EmbeddedLink"
+ },
+ "self": {
+ "$ref": "#/$defs/EmbeddedLink"
+ }
+ },
+ "type": "object"
+ }
+ },
+ "type": "object"
+}v0.40.0v0.34.0v0.27.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is structured. The description adds that the reset applies to all roles and restores factory defaults, but it does not explain whether custom roles are deleted, how users or teams are affected, whether permissions are required, or how irreversible the operation is.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very short and front-loads the action and scope. The 'Toolset: Admin' and 'Parameters: None' metadata are somewhat redundant, but they do not obscure the core sentence.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a destructive global admin operation, the description is minimally adequate but omits important context about authorization requirements, scope of impact, and reversibility. The presence of an output schema means return values need not be described, but the operational consequences still deserve more coverage.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters and the schema is empty, so the parameter baseline is 4. The description explicitly says there are no parameters, which is consistent with the schema and leaves no ambiguity.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: reset all roles to their factory defaults. This clearly distinguishes it from sibling tools that create, update, delete, or list individual roles. It is not quite a 5 because it does not explicitly name the alternative operations or clarify what 'factory defaults' excludes.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives such as updating or deleting individual roles. It gives no prerequisites, exclusions, or warning conditions, leaving the agent to infer that this is a global admin operation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.