Skip to main content
Glama
Sign In
vCFD

vCFD

by gpu7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

delete_case

Permanently delete a CFD case directory. Requires confirmation to prevent accidental data loss and free up storage space.

Instructions

Permanently delete a case directory. Requires confirm=true.

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": {
      "case_name": "<case_name>"
    },
    "name": "delete_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
case_nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 burden. It clearly discloses the destructive, irreversible nature ('Permanently delete') and the mandatory confirm flag, which are the most critical behavioral traits for a deletion tool. It omits side effects or failure modes, but the disclosure is still strong.

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 concise sentences, front-loaded with the action, and every word adds value. No redundancy or filler.

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?

The tool is simple, and an output schema exists, so return values are covered elsewhere. The description covers the core destructive action and safety requirement. It lacks a contrast with clean_case and potential side effects, but for a straightforward delete operation, it is nearly complete.

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 0%, so the description must compensate. It explains confirm must be true, adding meaning to that parameter. However, case_name is left to its self-evident name, and the behavior when confirm is false is only implied, not stated. Partial compensation.

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?

The description uses a specific verb ('delete') and a clear resource ('case directory'), making the action unambiguous. The word 'Permanently' adds important irreversible context and differentiates it from non-destructive operations like clean_case.

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?

No guidance is given for when to use this tool versus alternatives like clean_case or describe_case. The only usage-related instruction is 'Requires confirm=true', which is an invocation detail, not a selection guideline.

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