Skip to main content
Glama
ohneben

ohneben's Wafeq MCP

wafeq_purchase_orders_line_items_create

Create a purchase order line item by supplying the purchase order ID and item details (description, quantity, unit amount). Use an idempotency key to prevent duplicate records on retry.

Instructions

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

Create purchase order line item

Endpoint for creating a new purchase order line item.

Not idempotent โ€” calling twice creates two records. Pass idempotency_key (or let the server generate one) to make a retry safe.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesAugment ``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

A3.7/5.0
Behavior4/5

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

Annotations already signal non-idempotent and readOnlyHint=false, but the description adds meaningful behavioral context: calling twice creates two records, and idempotency_key (or server-generated UUID) makes retries safe. This is useful beyond the structured annotations.

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 front-loaded with the WRITE marker and endpoint, but it contains redundancy: 'Create purchase order line item' is repeated as a heading and again in the sentence 'Endpoint for creating a new purchase order line item.' The idempotency note is valuable, but the duplicate-purpose lines could be tightened.

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?

Given a nested body and no output schema, the description is only moderately complete. It explains the endpoint and idempotency well, but it does not mention what happens on success, what response to expect, or that purchase_order_id must reference an existing purchase order. Required body fields are left entirely to the schema.

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 itself documents most body fields. The description adds some value by explaining idempotency_key behavior, but it does not clarify purchase_order_id or the overall body structure beyond what the schema already provides. This is adequate but not strongly compensating.

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 clearly states a specific action and resource: 'Create purchase order line item' with the explicit POST endpoint. The verb 'create' and resource 'purchase order line item' distinguish it from sibling list/retrieve/update/destroy tools without ambiguity.

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?

Usage is implied by the endpoint and phrasing: this is the tool for adding a new line item to a purchase order. However, it does not explicitly contrast with sibling tools like update, list, or destroy, nor does it state when one should prefer another line-item operation.

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