ohneben's Wafeq MCP

wafeq_branches_update

Idempotent

Modify an existing Wafeq branch's data—address, name, phone, city, and more—to fix errors and keep branch information current.

Instructions

🟡 WRITE · updates data · Branches · PUT /branches/{id}/

Update branch

Endpoint for updating an existing branch.

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>",
      "body": "<body>"
    },
    "name": "wafeq_branches_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
`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

C2.5/5.0

Behavior2/5

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

The annotations already convey readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description only restates the write nature with 'WRITE' and 'updates data' and adds the endpoint, without disclosing behavioral context such as whether omitted fields are reset, what side effects occur, or any authorization requirements. No contradiction exists, but no meaningful behavioral detail is added.

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 highly repetitive: 'WRITE · updates data · Branches · PUT /branches/{id}/', 'Update branch', and 'Endpoint for updating an existing branch' all say essentially the same thing. The redundancy wastes space and adds no new information beyond the first line.

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 nested required body fields, no output schema, and a sibling partial_update tool, the description should clarify full-replacement behavior and distinguish this from partial updates. It does neither. The annotations cover idempotency and non-destructiveness, but the description leaves important operational context missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description does not explain any parameters. Schema coverage is 67%, but the body parameter's description is generic serializer boilerplate, and the top-level 'id' has no description. The nested field descriptions in the schema carry most of the meaning, so the description provides no additional semantic value for parameters.

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 states a specific action ('updating') and resource ('branch'), and the explicit PUT endpoint identifies this as the full-update operation rather than a create or partial update. However, it does not explicitly name or contrast sibling tools like wafeq_branches_partial_update or wafeq_branches_create, so differentiation is implicit rather than stated.

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?

The description provides no guidance on when to choose this tool over alternatives such as wafeq_branches_create, wafeq_branches_partial_update, or wafeq_branches_destroy. It does not mention prerequisites, full-vs-partial replacement semantics, or any condition that should trigger its use.

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

Deploy Server