Skip to main content
Glama
ohneben

ohneben's Wafeq MCP

wafeq_purchase_orders_line_items_partial_update

Idempotent

Partially update a purchase order line item by changing only the fields you specify, such as quantity, unit amount, discount, tax rate, or custom fields, without affecting other line item data.

Instructions

๐ŸŸก WRITE ยท updates data ยท Purchase Order Line Items ยท PATCH /purchase-orders/{purchase_order_id}/line-items/{id}/

Partial update purchase order line item

Endpoint for partially updating an existing purchase order line item.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
bodyNoAugment ``custom_fields`` in the output with computed CALCULATED field values. Apply to any line-item serializer whose model has ``get_resolved_custom_fields``.
idempotency_keyNoOptional 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.
purchase_order_idYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv2.0.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already carry readOnlyHint=false, idempotentHint=true, and destructiveHint=false, and the description merely repeats that this is a write/update operation without adding behavioral details such as that omitted fields are left unchanged. It does not contradict the annotations, but it also contributes no new behavioral context.

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?

Three sentences are present, but the last two ('Partial update purchase order line item' and 'Endpoint for partially updating...') are near-duplicates, so not every sentence earns its place. The first badge line is informative, but the redundancy and lack of additional detail make the structure weak.

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?

There is no output schema and the description does not say what the endpoint returns. It also omits partial-update semantics (only included fields change), prerequisites, and any error/edge-case context, leaving the agent to infer important behavior from the tool name alone.

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 adds no parameter guidance; required path parameters id and purchase_order_id are undocumented in the schema, and the body parameter has a confusing serializer-oriented note about augmenting custom_fields output rather than explaining that it contains the fields to update. The idempotency_key is well explained in the schema, but the description itself fails to clarify the body semantics.

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 the operation as 'Partial update purchase order line item' and includes the HTTP method (PATCH) and resource path, making it unambiguous which resource is being modified. It does not explicitly name sibling alternatives, so it stops short of a 5.

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 word 'partial' and the endpoint design imply this tool should be used to update a subset of fields on an existing purchase order line item, but the description never states when to use it versus the full-update sibling or other line-item tools. No alternatives or exclusions are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ohneben/Wafeq-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server