Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

purchase_order_lines_find

Retrieve purchase order lines by order number, item, vendor, or other filters to inspect line-level details.

Instructions

Find Purchase Order Lines.

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": "purchase_order_lines_find"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
skipNo
orderNo
fieldsNo
distinctNo
divisionNo
pageSizeNo
countOnlyNo
ItemNumberNo
totalCountNo
OrderNumberNo
VendorNumberNo
StockLocationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

D1.3/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden and supplies nothing: no statement about pagination, default result size, filtering semantics, or what is returned. A read-only find is the likely intent, but that is inferred from the verb rather than disclosed.

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?

The single sentence contains no wasted words, but that is because it contains almost no information. Brevity here reflects under-specification rather than disciplined editing.

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

Completeness1/5

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

For a 13-parameter query tool with no annotations, no output schema, and no parameter documentation, the definition is far too thin. An agent cannot determine how to construct a useful query or what the response contains.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Thirteen parameters exist with 0% schema description coverage, and the description adds no meaning for any of them. The agent gets no guidance on the distinction between page/skip/pageSize, how order and fields strings are formatted, or how countOnly/totalCount interact with distinct.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Find Purchase Order Lines" is a verb-plus-resource phrase that simply restates the tool name with no additional scope, no indication of what attributes can be searched, and no differentiation from sibling find tools such as customer_order_lines_find or purchase_orders_find.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no mention of prerequisites, no exclusions, and no pointer to the sibling create/get/update/delete tools or the analogous customer_order_lines_find. The agent must infer everything from the 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