Skip to main content
Glama
Sign In
SmartBear MCP server

SmartBear MCP server

Official
by SmartBear
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Contract Testing: Admin Update Team

contract-testing_admin_update_team
Idempotent

Replaces a contract testing team's configuration, including name, administrators, environments, and pacticipants, to keep access and assignments current.

Instructions

Replace a team's configuration (admin).

Toolset: Admin

Parameters:

  • teamId (string) required: UUID of the team to update

  • name (string) required: Name of the team

  • administratorUuids (array): UUIDs of team administrators

  • environmentUuids (array): UUIDs of environments assigned to this team

  • pacticipantNames (array): Names of pacticipants assigned to this team

Input Schema

NameRequiredDescriptionDefault
nameYesName of the team
teamIdYesUUID of the team to update
environmentUuidsNoUUIDs of environments assigned to this team
pacticipantNamesNoNames of pacticipants assigned to this team
administratorUuidsNoUUIDs of team administrators

Output Schema

NameRequiredDescriptionDefault
nameNo
uuidNo
_linksNo
_embeddedNo
createdAtNo
updatedAtNo
numberOfMembersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.43.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "EmbeddedEnvironment": {
+      "additionalProperties": {},
+      "properties": {
+        "_links": {
+          "additionalProperties": {},
+          "properties": {
+            "self": {
+              "$ref": "#/$defs/EmbeddedLink"
+            }
+          },
+          "type": "object"
+        },
+        "createdAt": {
+          "type": "string"
+        },
+        "displayName": {
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        },
+        "production": {
+          "type": "boolean"
+        },
+        "updatedAt": {
+          "type": "string"
+        },
+        "uuid": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "EmbeddedLink": {
+      "additionalProperties": {},
+      "properties": {
+        "href": {
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        },
+        "templated": {
+          "type": "boolean"
+        },
+        "title": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "EmbeddedNamed": {
+      "additionalProperties": {},
+      "properties": {
+        "_links": {
+          "additionalProperties": {},
+          "properties": {
+            "self": {
+              "$ref": "#/$defs/EmbeddedLink"
+            }
+          },
+          "type": "object"
+        },
+        "name": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "EmbeddedUser": {
+      "additionalProperties": {},
+      "properties": {
+        "_links": {
+          "additionalProperties": {},
+          "properties": {
+            "self": {
+              "$ref": "#/$defs/EmbeddedLink"
+            }
+          },
+          "type": "object"
+        },
+        "active": {
+          "type": "boolean"
+        },
+        "email": {
+          "type": "string"
+        },
+        "firstName": {
+          "type": "string"
+        },
+        "identityProviderId": {
+          "type": "string"
+        },
+        "lastName": {
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        },
+        "uuid": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "_embedded": {
+      "additionalProperties": {},
+      "properties": {
+        "administrators": {
+          "items": {
+            "$ref": "#/$defs/EmbeddedUser"
+          },
+          "type": "array"
+        },
+        "environments": {
+          "items": {
+            "$ref": "#/$defs/EmbeddedEnvironment"
+          },
+          "type": "array"
+        },
+        "pacticipants": {
+          "items": {
+            "$ref": "#/$defs/EmbeddedNamed"
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
+    },
+    "_links": {
+      "additionalProperties": {},
+      "properties": {
+        "self": {
+          "$ref": "#/$defs/EmbeddedLink"
+        }
+      },
+      "type": "object"
+    },
+    "createdAt": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "numberOfMembers": {
+      "type": "number"
+    },
+    "updatedAt": {
+      "type": "string"
+    },
+    "uuid": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Addedv0.40.0
  3. Removedv0.34.0
  4. First observedv0.27.1

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare idempotent=true, destructive=false and non-readOnly, so the safety profile is covered. The description's one addition is the word "Replace", which hints at full-overwrite semantics beyond what annotations say, but it never clarifies whether omitted arrays (administrators, environments, pacticipants) are cleared or left untouched — the single most consequential behavioral fact here.

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 verb phrase is efficient, but the entire parameter list duplicates structured schema data and the "Toolset: Admin" line adds nothing the name doesn't. Roughly half the text is redundant.

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 and annotations exist, so return values and safety need not be explained. Still, for a destructive-ish configuration replacement the description leaves open whether this is a merge or a full overwrite and gives no alternative-tool routing, which an agent needs to call it correctly.

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 description's parameter block is a near-verbatim restatement of the schema, adding no format, constraint, or interaction detail. Baseline 3 applies since the schema already 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 ("Replace") and resource ("a team's configuration"), which distinguishes it from read-only siblings like contract-testing_admin_get_team and from create/delete team tools. However, it does not distinguish it from the closely related patch_team_users and set_team_users siblings, which operate on the same team entity.

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 at all beyond the "(admin)" tag. With siblings such as contract-testing_admin_patch_team_users, contract-testing_admin_set_team_users, and contract-testing_admin_create_team in the same family, an agent has no statement of which one to pick or what preconditions apply.

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