ohneben's Wafeq MCP

wafeq_items_destroy

DestructiveIdempotent

Permanently delete an item by its ID. This irreversible action removes the item record from the system.

Instructions

🔴 DESTRUCTIVE · deletes · Items · DELETE /items/{id}/

Delete item

Endpoint for deleting an existing item.

Permanently removes the record.

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": {
      "id": "<id>"
    },
    "name": "wafeq_items_destroy"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`idempotency_key`	No	Optional idempotency key (sent as the X-Wafeq-Idempotency-Key header). A UUID v4 is generated automatically when omitted, so an automatic network retry can never duplicate this operation. Pass your own stable value to make a deliberate re-invocation safe as well.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Sep 8, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Beyond the annotations, the description adds that the operation 'permanently removes the record' and labels it 'DESTRUCTIVE', clarifying irreversibility. It does not mention cascading effects or authorization, but the annotations already cover readOnly/destructive/idempotent traits, so the additional behavioral detail is sufficient.

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?

The description is short and front-loaded with the endpoint and destructive marker, but it repeats the same idea multiple times ('Delete item', 'Endpoint for deleting an existing item'). The redundancy reduces the value of otherwise compact text.

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?

For a simple destructive action with no output schema, this is complete enough: it states the operation, endpoint, permanence, and the idempotency behavior is covered by the schema. Missing details such as consequences for related records are not critical at this level of complexity.

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?

The schema documents `idempotency_key` well, while `id` has no schema description; the description's DELETE /items/{id}/ path only implicitly conveys that `id` identifies the item to delete. This is adequate but not a rich parameter explanation, and the description adds no explicit parameter guidance.

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 clearly identifies a specific verb ('deletes'), resource ('Items'), and effect ('Permanently removes the record'), and includes the endpoint DELETE /items/{id}/. This distinguishes it from sibling item tools like retrieve/update/partial_update, which do not remove the record.

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?

No explicit when-to-use or when-not-to-use guidance is given, and no alternative tools are named. The intended usage is implied by 'Endpoint for deleting an existing item', which is sufficient for a simple destroy operation but does not discuss exclusions or fallback tools.

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

Deploy Server