Skip to main content
Glama
Sign In
ohneben's Wafeq MCP

ohneben's Wafeq MCP

by ohneben
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

wafeq_purchase_orders_line_items_list

Read-onlyIdempotent

Retrieve line items for a purchase order by its ID, with optional pagination for large result sets.

Instructions

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

List purchase order line items

Endpoint for retrieving a list of purchase order line items.

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>"
    },
    "name": "wafeq_purchase_orders_line_items_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoA page number within the paginated result set.
page_sizeNoNumber of results to return per page.
purchase_order_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the description's '🟢 READ-ONLY' merely restates that. It does add the exact HTTP method and resource path (GET /purchase-orders/{purchase_order_id}/line-items/), which is mildly useful, but it discloses nothing about pagination behavior or response shape. No contradiction with 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 header line is compact and front-loaded with the READ-ONLY signal and endpoint. But the final two sentences are redundant: 'List purchase order line items' and 'Endpoint for retrieving a list of purchase order line items' say the same thing, and the annotation title already repeats it as well.

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 simple three-parameter list tool with rich annotations, this is nearly adequate: it names the endpoint, the parent resource, and the pagination parameters are visible in the schema. However, with no output schema it never describes what fields each line item contains, and there is no note on pagination semantics or any ordering/filtering behavior.

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 coverage is 67% — page and page_size already have descriptions, and the description adds nothing about them. However, the endpoint path clarifies that the undocumented required purchase_order_id parameter is the parent purchase order's identifier, partially compensating for that schema gap.

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?

States a specific verb and resource ('List purchase order line items') and gives the exact endpoint path, making the scope unambiguous. The word 'list' inherently distinguishes it from the singleton retrieve/create/update/destroy siblings for the same resource, though it never names them explicitly.

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?

Provides no guidance on when to choose this tool over the many sibling line-item tools (wafeq_purchase_orders_line_items_retrieve, _create, _update, _destroy, _partial_update, plus equivalent lists for bills, invoices, and quotes). There is no when-to-use, when-not-to-use, or alternative routing — the agent must infer selection from the tool name alone.

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

Deploy Server

Other Tools