ohneben's Wafeq MCP

wafeq_quotes_invoice_create

Convert an accepted quote into a new invoice. Provide the quote ID to create the corresponding invoice record.

Instructions

🟡 WRITE · creates data · Quotes · POST /quotes/{id}/invoice/

Convert quote to invoice

This endpoint can be used to convert a quote to an invoice.

Not idempotent — calling twice creates two records. Pass idempotency_key (or let the server generate one) to make a retry safe.

Creates a NEW invoice from the quote. Calling twice creates two invoices — pass an idempotency_key if you may retry.

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_quotes_invoice_create"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes

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?

Annotations already declare non-idempotence, but the description adds concrete consequences: calling twice creates two records/invoices, and suggests passing an idempotency_key for safe retries. This is useful behavioral context beyond the structured annotations.

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

Conciseness2/5

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

The description is repetitive: 'Convert quote to invoice', 'This endpoint can be used to convert a quote to an invoice', and 'Creates a NEW invoice from the quote' all say the same thing. The non-idempotency warning is also stated twice, making the text longer than necessary.

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 one-parameter tool, the description provides enough to understand the operation and key retry risk. However, it is incomplete around the 'id' parameter semantics and the idempotency_key guidance is not backed by the schema, which could prevent an agent from invoking it exactly as described.

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 has one undocumented 'id' parameter and 0% description coverage. The description implies via the endpoint path that 'id' is the quote ID, but it never explicitly states this or explains format/constraints. It also mentions idempotency_key, which is not present in the input schema, adding minor confusion.

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 action and resource: 'Convert quote to invoice' and 'Creates a NEW invoice from the quote', backed by the endpoint path POST /quotes/{id}/invoice/. This clearly differentiates from generic quote CRUD or invoice creation 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?

The description gives clear context for when to use the tool: converting a quote into an invoice. It does not explicitly discuss alternatives or exclusions, but the intended use case is unambiguous enough for an agent to select it correctly.

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

Deploy Server