ohneben's Wafeq MCP

wafeq_bills_line_items_create

Creates a new line item on an existing bill in Wafeq. Provide account, description, quantity, unit amount, and optional tax rate, discount, or amortization to record bill details accurately.

Instructions

🟡 WRITE · creates data · Bill Line Items · POST /bills/{bill_id}/line-items/

Create bill line item

Endpoint for creating a new bill line item.

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

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": {
      "bill_id": "<bill_id>",
      "body": "<body>"
    },
    "name": "wafeq_bills_line_items_create"
  }
}

Input Schema

Name	Required	Description
`body`	Yes	Augment ``custom_fields`` in the output with computed CALCULATED field values. Apply to any line-item serializer whose model has ``get_resolved_custom_fields``.
`bill_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

A4/5.0

Behavior4/5

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

Annotations already indicate a non-read, non-idempotent write operation. The description goes beyond that by explicitly stating that calling twice creates two records and explaining how the idempotency_key makes retries safe. This adds concrete behavioral safety context without contradicting any annotation.

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 compact and front-loads the endpoint, but it repeats itself: 'Create bill line item' and 'Endpoint for creating a new bill line item' say the same thing. The idempotency paragraph is valuable, but the opening could be trimmed without losing meaning.

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 create operation with a nested body object and no output schema, the description provides the essential endpoint, verb, and non-idempotency warning, while the schema covers parameter details. It does not explain why to choose this over update or list siblings, but the create-focused purpose and schema richness are largely sufficient.

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 input schema already documents most parameters, including idempotency_key behavior, and the required body fields are clear. The description adds little beyond what the schema provides; the idempotency_key note is useful but largely duplicates the schema's own parameter description.

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 explicitly identifies the operation ('Create bill line item'), the resource ('Bill Line Items'), and the exact endpoint (POST /bills/{bill_id}/line-items/). This clearly separates it from other line-item tools for invoices, purchase orders, or 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 Guidelines4/5

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

The description clearly frames the tool as the endpoint for creating a new bill line item, making the primary use case obvious. It does not name sibling update/retrieve/destroy tools as alternatives, but the create-vs-manage distinction is clear enough from the stated purpose.

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

Deploy Server