ohneben's Wafeq MCP

wafeq_payslips_pay_items_update

Idempotent

Update an existing pay item on a payslip by specifying the payslip ID, pay item ID, and the new account, amount, and description.

Instructions

🟡 WRITE · updates data · Pay Items · PUT /payslips/{payslip_id}/pay-items/{id}/

Update pay item

Endpoint for updating an existing pay item.

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>",
      "id": "<id>",
      "body": "<body>"
    },
    "name": "wafeq_payslips_pay_items_update"
  }
}

Input Schema

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

Behavior3/5

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

Annotations already declare this as a write (readOnlyHint=false) and idempotent. The description adds the HTTP PUT method and resource path, but does not disclose behavioral details such as whether the entire pay item is replaced or how missing resources are handled. No contradiction with 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 short but redundant: '🟡 WRITE · updates data', 'Update pay item', and 'Endpoint for updating an existing pay item' all say the same thing. It is front-loaded but contains unnecessary repetition.

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?

With no output schema, the description should at least hint at the response or any side effects. More importantly, it does not clarify that this is a full replacement-style PUT update, which is essential given the existence of a sibling partial_update tool. This leaves selection and invocation partially ambiguous.

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 coverage is 50%, but the inline URL pattern /payslips/{payslip_id}/pay-items/{id}/ gives semantic meaning to the otherwise undocumented path parameters. The schema already documents the body fields and idempotency_key, so the description adequately compensates for the coverage gap.

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 clearly identifies the operation as an update to a pay item within a payslip, reinforced by the URL pattern and the repeated phrase 'updating an existing pay item.' It does not, however, explicitly distinguish itself from the sibling partial_update tool.

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?

No guidance is given on when to use this full update versus the sibling partial_update or when an update is appropriate. The statement 'updates data' adds no practical selection criteria.

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

Deploy Server