ohneben's Wafeq MCP

wafeq_accounts_partial_update

Idempotent

Update selected fields of an existing account—such as name, type, classification, or parent—while preserving all other account details.

Instructions

🟡 WRITE · updates data · Accounts · PATCH /accounts/{id}/

Partial update account

Endpoint for partially updating an existing account.

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

Input Schema

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

Behavior3/5

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

Annotations already carry the key safety signals (readOnlyHint=false, destructiveHint=false, idempotentHint=true), so the bar is lower. The description adds that this is a PATCH/partial update, but it does not disclose further behavioral details such as what happens to omitted fields or what the response contains.

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

Conciseness4/5

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

The description is short and front-loaded with a write indicator and endpoint. However, 'Partial update account' and 'Endpoint for partially updating an existing account' are redundant restatements of each other and of the annotation title.

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 PATCH operation with a complex optional body and no output schema, the description is minimally sufficient: it states the resource and partial-update semantics, and the schema covers field details. It lacks guidance on full-update alternatives, return behavior, and the effect of omitting fields.

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 the nested body fields and idempotency key reasonably well. The description only adds path context for the required id via '/accounts/{id}/'; it does not clarify the body object or compensate for the boilerplate serializer 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 states a specific verb ('updates'), a concrete resource ('Accounts'), the HTTP method and path ('PATCH /accounts/{id}/'), and the exact scope ('partially updating'). This clearly distinguishes the tool from retrieve, full update, and destroy siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description implies the tool is for modifying selected fields of an existing account rather than replacing the whole record, but it does not explicitly say when to choose wafeq_accounts_update instead, nor does it provide prerequisites or when-not-to-use guidance. It is adequate but leaves comparison to alternatives implicit.

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

Deploy Server