ohneben's Wafeq MCP

wafeq_quotes_line_items_destroy

DestructiveIdempotent

Permanently delete a line item from a Wafeq quote by providing the quote ID and line-item ID, removing unwanted entries from the document.

Instructions

🔴 DESTRUCTIVE · deletes · Quote Line Items · DELETE /quotes/{quote_id}/line-items/{id}/

Delete quote line item

Endpoint for deleting an existing quote line 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": {
      "quote_id": "<quote_id>",
      "id": "<id>"
    },
    "name": "wafeq_quotes_line_items_destroy"
  }
}

Input Schema

Name	Required	Description
`id`	Yes
`quote_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.7/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description reinforces this with the '🔴 DESTRUCTIVE' warning and 'Permanently removes the record.' That adds irreversibility context beyond the annotation flags. It does not contradict the idempotentHint or openWorldHint annotations.

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-loads the danger signal and endpoint, but 'Delete quote line item' and 'Endpoint for deleting an existing quote line item' are redundant restatements. Combining these into one sentence would make the description tighter.

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 simple delete call with robust annotations and no output schema, the description gives the essential behavior and permanence. It remains incomplete in not describing when to use it versus the many other line-item destroy tools or what response or errors to expect after deletion.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%, but the endpoint template explicitly shows {quote_id} and {id} as the parent quote and line item identifiers, adding meaning that the bare schema property names lack. The only schema-described parameter, idempotency_key, already has a thorough schema description, so no additional detail is required there.

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 states a specific verb ('deletes'/'Delete') and object ('Quote Line Items'), and includes the endpoint template 'DELETE /quotes/{quote_id}/line-items/{id}/'. This makes the target resource unambiguous and distinguishes it from the many sibling line-item destroy tools such as bills, purchase orders, and credit notes.

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 guidance about when to use this tool instead of the many sibling destroy endpoints or what preconditions apply. The description only restates the operation ('delete an existing quote line item') without exclusions, alternatives, or contextual cues such as 'only for quote line items'.

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

Deploy Server