RunWhen Platform MCP

Delete Assistant

delete_assistant

Soft-delete an AI assistant (persona) from a RunWhen workspace. Persona-scoped rules and commands are not removed automatically, so clean them up separately if no longer needed.

Instructions

Delete (soft-delete) an AI assistant (persona) from a workspace.

Persona-scoped rules and commands attached to this assistant are not removed automatically — clean them up separately if no longer needed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace_name": "<workspace_name>",
      "assistant_name": "<assistant_name>"
    },
    "name": "delete_assistant"
  }
}

Input Schema

Name	Required	Description	Default
`assistant_name`	Yes	Assistant short name to delete (e.g. 'azure-devops'). Workspace prefix optional.
`workspace_name`	Yes	The workspace the assistant belongs to.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 7, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the full disclosure burden and does so unusually well for a mutation: it reveals the operation is a soft-delete (recoverable/not a hard purge) and that attached persona-scoped rules and commands are NOT cascade-deleted. It omits auth/permission requirements and whether confirmation is needed, which keeps it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler, with the destructive/soft-delete nature front-loaded and the non-cascading caveat immediately after. Every clause carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and the two required params are fully covered by the schema. The description supplies the two most important behavioral facts (soft-delete, no cascade) for a low-complexity deletion tool; only permission/auth context is missing.

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% for both parameters, so the schema already documents workspace_name and assistant_name (including the optional workspace prefix). The description adds no parameter-level meaning beyond what the schema provides, 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?

The description states a specific verb and resource ('Delete (soft-delete) an AI assistant (persona)') and scopes it to a workspace, which cleanly separates it from create_assistant and update_assistant. It does not explicitly name any sibling or contrast behavior, so it stops just short of full differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by 'if no longer needed', with no explicit statement of when to prefer this over update_assistant or how to handle the case where the assistant is still referenced. It does at least flag the follow-up cleanup of persona-scoped rules and commands, which is genuine usage-relevant context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server