Skip to main content
Glama
verifyax

VerifyAX MCP

Official
by verifyax
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete scenario

delete_scenario
DestructiveIdempotent

Permanently deletes a VerifyAX scenario by UUID. Fails if simulation runs still reference it, and returns deletion confirmation; this action cannot be undone.

Instructions

Permanently deletes a scenario from your VerifyAX workspace by its uuid. This cannot be undone and fails if simulation runs still reference the scenario. Returns confirmation of the deletion.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scenario_uuidYesThe uuid of the scenario to permanently delete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.7
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Addedv1.0.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, yet the description still adds meaningful context: the deletion is permanent and cannot be undone, and it is blocked while simulation runs reference the scenario. The only omission is confirmation of return shape, which is mentioned but not detailed.

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?

Three tight sentences, front-loaded with the action and resource, then the irreversibility/constraint, then the response. No filler.

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

Completeness5/5

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

For a single-parameter destructive tool, the description covers permanence, the referential failure mode, and the return outcome. Nothing an agent needs before invoking it 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?

One parameter with 100% schema description coverage; the schema already documents scenario_uuid fully. The description only restates that the uuid identifies the scenario, adding no format or sourcing detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (permanently deletes), resource (scenario), and scope (by uuid, in the VerifyAX workspace). It is clearly distinguishable from sibling delete_agent and from read/list tools.

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

Usage Guidelines4/5

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

Gives a clear precondition for use and failure: it fails if simulation runs still reference the scenario. It does not name an alternative tool or spell out when-not-to-use beyond that precondition, but the context is unambiguous.

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