ohneben's Wafeq MCP

wafeq_payslips_pay_items_create

Create a pay item on a Wafeq payslip by supplying account, amount, and description. Use this to add earnings or deductions to payroll records.

Instructions

🟡 WRITE · creates data · Pay Items · POST /payslips/{payslip_id}/pay-items/

Create pay item

Endpoint for creating a new pay 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": {
      "payslip_id": "<payslip_id>",
      "body": "<body>"
    },
    "name": "wafeq_payslips_pay_items_create"
  }
}

Input Schema

Name	Required	Description
`body`	Yes	A ModelSerializer that takes additional arguments for "fields", "omit" and "expand" in order to control which fields are displayed, and whether to replace simple values with complex, nested serializations
`payslip_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

B3.2/5.0

Behavior4/5

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

The description adds practical value beyond the annotations by explaining that calling twice creates two records and that an idempotency_key (or server-generated UUID) makes retries safe. This is consistent with idempotentHint=false and readOnlyHint=false, so there is no contradiction.

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 write indicator and endpoint, but 'Create pay item' and 'Endpoint for creating a new pay item' are redundant. The idempotency sentence is useful and placed at the end.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a create tool with a nested body and no output schema, the description does not mention required body fields, payslip prerequisites, or what the response will be. The idempotency guidance is helpful, but the overall context is thin.

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 description coverage is 67%, and the schema already documents body fields and idempotency_key in detail. The description adds little beyond naming idempotency_key for safe retries; payslip_id remains directly undocumented, though the endpoint path provides some context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Create pay item' and provides the explicit endpoint POST /payslips/{payslip_id}/pay-items/, making the operation specific and concrete. It is clearly the create operation among the sibling pay-item tools, though it does not explicitly contrast itself with them.

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 on when to prefer this tool over list/retrieve/update/destroy, nor any preconditions such as the payslip having to exist. The idempotency note is useful for retry behavior but does not help with tool selection.

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

Deploy Server