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

ohneben's Wafeq MCP

by ohneben
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

wafeq_purchase_orders_list

Read-onlyIdempotent

List and filter purchase orders by branch, status, contact, project, date, or reference. Returns paginated results for reviewing procurement records.

Instructions

🟢 READ-ONLY · Purchase Orders · GET /purchase-orders/

List purchase orders

Endpoint for retrieving a list of purchase orders.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wafeq_purchase_orders_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoA page number within the paginated result set.
branchNoThe unique identifier of the branch.
statusNoThe status of the purchase order.
contactNoThe unique identifier of the contact.
projectNoThe unique identifier of the project.
page_sizeNoNumber of results to return per page.
referenceNoReference.
external_idNoExternal identifier.
created_ts_afterNoThe timestamp in UTC when the purchase order was created.
created_ts_beforeNoThe timestamp in UTC when the purchase order was created.
modified_ts_afterNoThe timestamp in UTC when the purchase order was last modified.
modified_ts_beforeNoThe timestamp in UTC when the purchase order was last modified.
purchase_order_dateNoThe date of the purchase order.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description's 'READ-ONLY' label adds no new safety information. It also does not disclose behavioral details like pagination behavior, filtering semantics, or response format.

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 short and front-loaded with the read-only and endpoint metadata. However, 'List purchase orders' and 'Endpoint for retrieving a list of purchase orders' are redundant, and the saved space could have been used for more useful guidance.

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 read-only list operation with no required parameters, this is minimally viable. However, with 13 optional filters and many sibling list tools, the description does not clarify pagination, response shape, or when to prefer this tool over related purchase-order endpoints.

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 100%, so the baseline applies: every parameter has some schema-level documentation. The description itself adds no parameter context, but the schema already carries the documentation burden.

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 states a clear action and resource: 'List purchase orders' with the endpoint 'GET /purchase-orders/'. It is unambiguous, but it does not explicitly distinguish itself from sibling tools like wafeq_purchase_orders_retrieve or wafeq_purchase_orders_line_items_list.

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?

There is no guidance on when to use this tool versus alternatives, such as retrieving a single purchase order or listing line items. The intended usage is only implied by the word 'List' in the name and title.

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