Skip to main content
Glama
Sign In
SmartBear MCP server

SmartBear MCP server

Official
by SmartBear
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Contract Testing: Delete Pacticipant

contract-testing_delete_pacticipant
DestructiveIdempotent

Deletes a pacticipant and all associated data from contract testing, removing the specified participant and its related records in one action.

Instructions

Delete a pacticipant and all its associated data.

Toolset: Pacticipants

Parameters:

  • pacticipantName (string) required: Name of the pacticipant to delete

Input Schema

NameRequiredDescriptionDefault
pacticipantNameYesName of the pacticipant to delete

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 and readOnlyHint=false, so the safety profile is covered. The description adds real value with 'and all its associated data', disclosing cascade behavior, but omits irreversibility, confirmation requirements, or auth scope.

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 operation and its destructive scope are front-loaded in one sentence with no wasted prose. The trailing toolset/parameter block duplicates the schema slightly but keeps structure readable.

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 destructive single-parameter tool with an output schema present, the description covers what is deleted but not the risk profile an agent most needs (irreversible? requires elevated permission?). Adequate but with a clear gap for a high-blast-radius 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 coverage is 100% and there is a single parameter already documented in the schema. The description merely restates the parameter block, adding no identification-format or naming-convention detail beyond it, 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 (Delete) and resource (pacticipant) and adds scope: 'and all its associated data'. That distinguishes it from soft-mutation siblings like contract-testing_update_pacticipant or contract-testing_patch_pacticipant, though no sibling is named 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 explicit guidance on when to use this versus the sibling mutation tools (update/patch/create pacticipant) or on prerequisites such as required permissions. Usage must be inferred from the tool name and the cascade phrase alone.

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