Skip to main content
Glama
Sign In
SmartBear MCP server

SmartBear MCP server

Official
by SmartBear
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Contract Testing: Admin Create System Account

contract-testing_admin_create_system_account

Create a new admin system account for SmartBear contract testing by specifying its name. Use this to provision system-level access for test administration.

Instructions

Create a new system account (admin).

Toolset: Admin

Parameters:

  • name (string) required: Name of the system account

Input Schema

NameRequiredDescriptionDefault
nameYesName of the system account

Output Schema

NameRequiredDescriptionDefault
nameNo
typeNo
uuidNo
emailNo
_linksNo
activeNo
lastNameNo
seatTypeNo
_embeddedNo
createdAtNo
firstNameNo
lastLoginNo
updatedAtNo
externalIdNo
externalIdpIdNo
typeDescriptionNo
identityProviderIdNo
externalIdpUsernameNo
authenticationSourceNo
lastTimeTokenAccessedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.43.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "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"
+    },
+    "UserRole": {
+      "additionalProperties": {},
+      "properties": {
+        "_links": {
+          "additionalProperties": {},
+          "properties": {
+            "self": {
+              "$ref": "#/$defs/EmbeddedLink"
+            }
+          },
+          "type": "object"
+        },
+        "name": {
+          "type": "string"
+        },
+        "permissions": {
+          "items": {
+            "$ref": "#/$defs/Permission"
+          },
+          "type": "array"
+        },
+        "uuid": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "UserTeam": {
+      "additionalProperties": {},
+      "properties": {
+        "_links": {
+          "additionalProperties": {},
+          "properties": {
+            "pf:integrations": {
+              "$ref": "#/$defs/EmbeddedLink"
+            },
+            "pf:membership": {
+              "$ref": "#/$defs/EmbeddedLink"
+            },
+            "self": {
+              "$ref": "#/$defs/EmbeddedLink"
+            }
+          },
+          "type": "object"
+        },
+        "name": {
+          "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/UserRole"
+          },
+          "type": "array"
+        },
+        "teams": {
+          "items": {
+            "$ref": "#/$defs/UserTeam"
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
+    },
+    "_links": {
+      "additionalProperties": {},
+      "properties": {
+        "pf:tokens": {
+          "$ref": "#/$defs/EmbeddedLink"
+        },
+        "self": {
+          "$ref": "#/$defs/EmbeddedLink"
+        }
+      },
+      "type": "object"
+    },
+    "active": {
+      "type": "boolean"
+    },
+    "authenticationSource": {
+      "type": "string"
+    },
+    "createdAt": {
+      "type": "string"
+    },
+    "email": {
+      "type": "string"
+    },
+    "externalId": {
+      "type": "string"
+    },
+    "externalIdpId": {
+      "type": "string"
+    },
+    "externalIdpUsername": {
+      "type": "string"
+    },
+    "firstName": {
+      "type": "string"
+    },
+    "identityProviderId": {
+      "type": "string"
+    },
+    "lastLogin": {
+      "type": "string"
+    },
+    "lastName": {
+      "type": "string"
+    },
+    "lastTimeTokenAccessed": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "seatType": {
+      "type": "string"
+    },
+    "type": {
+      "anyOf": [
+        {
+          "const": 0,
+          "type": "number"
+        },
+        {
+          "const": 1,
+          "type": "number"
+        }
+      ]
+    },
+    "typeDescription": {
+      "type": "string"
+    },
+    "updatedAt": {
+      "type": "string"
+    },
+    "uuid": {
+      "type": "string"
+    }
+  },
+  "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 readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the safety profile is covered. The description adds essentially nothing beyond that — it does not mention required admin scope or permissions, what happens on duplicate name, or whether credentials/tokens are returned alongside the new account.

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?

The description is short and front-loads the action, which is good. However, the '**Toolset:** Admin' line and the parameter list duplicate structured fields already present in annotations and the input schema, so a portion of the text does not earn its place.

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?

The tool is simple (one required string parameter) with full schema coverage and an output schema, so return values need not be explained. Still, an agent gets no information about admin scope requirements or what a system account actually is, leaving a meaningful gap for a mutating admin operation.

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 there is a single parameter, and the description merely restates the schema's own text ('Name of the system account'). No added meaning about format, uniqueness constraints, or role assignment is provided, so the baseline of 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?

States a specific verb and resource ('Create a new system account'), which separates it from sibling admin tools such as create_user, create_team, and create_role. It does not explicitly distinguish itself from contract-testing_admin_get_system_account_tokens or explain how a 'system account' differs from a regular user account, so it falls short of a 5.

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 prerequisites, and no named alternatives. The '(admin)' marker hints that elevated privileges are required, but that is the only usage signal and it is never stated as a condition.

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