ohneben's Wafeq MCP

wafeq_purchase_orders_line_items_retrieve

Read-onlyIdempotent

Fetch a single line item from a Wafeq purchase order by providing the purchase order ID and line item ID. Use this read-only action to access detailed line item data.

Instructions

🟢 READ-ONLY · Purchase Order Line Items · GET /purchase-orders/{purchase_order_id}/line-items/{id}/

Retrieve purchase order line item

Endpoint for retrieving a single purchase order line 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": {
      "purchase_order_id": "<purchase_order_id>",
      "id": "<id>"
    },
    "name": "wafeq_purchase_orders_line_items_retrieve"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`purchase_order_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Sep 8, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, and the description reinforces the READ-ONLY/GET nature and shows the endpoint path. It adds no additional behavioral context such as authentication requirements, error behavior, or response characteristics, but it does not contradict the 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 compact and front-loaded, but 'Retrieve purchase order line item' and 'Endpoint for retrieving a single purchase order line item' are redundant restatements. The header line plus the repeated sentence could be merged without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only retrieval tool with two path parameters, the description and annotations provide enough information to call it correctly. It lacks explicit guidance about choosing this over sibling endpoints, but the 'single' qualifier and clear endpoint path make the primary calling intent clear despite no output schema.

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?

The schema only provides parameter names with no descriptions, so the endpoint path 'GET /purchase-orders/{purchase_order_id}/line-items/{id}/' adds meaning by showing that purchase_order_id identifies the parent purchase order and id identifies the specific line item. This compensates for the 0% schema description coverage, though it leaves value formats unspecified.

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 uses a specific verb and resource: 'retrieve purchase order line item' and explicitly says 'single', which distinguishes it from list/create/update/destroy siblings. The endpoint path clarifies it targets one line item nested under a purchase order.

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 it should be used when fetching a single purchase order line item by ID, but it never names sibling alternatives like the list endpoint or explains when not to use it. No explicit when-to-use or when-not-to-use guidance is provided.

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

Deploy Server