Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

customer_order_lines_find

Find customer order lines by order number, item number, customer number, location, division, or order type to retrieve matching sales order details and support order tracking.

Instructions

Find Customer Order Lines. Filter by OrderNumber, ItemNumber, CustomerNumber, etc.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
skipNo
fieldsNo
LocationNo
distinctNo
divisionNo
historicNo
pageSizeNo
OrderTypeNo
countOnlyNo
ItemNumberNo
totalCountNo
OrderNumberNo
CustomerNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, yet it discloses nothing beyond the bare read intent. It does not mention pagination defaults, result caps, sort order, whether historic records are included by default, or what countOnly/totalCount actually do — all material for a 14-parameter query tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the resource stated first and the filterable fields second — appropriately front-loaded and free of filler. The trailing "etc." is the one wasted element, since it signals more parameters exist without saying which.

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

Completeness2/5

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

For a 14-parameter tool with no annotations and no output schema, the description is far too thin: pagination, projection (fields), counting flags, and the historic toggle are all unexplained. The agent can tell what the tool retrieves but not how to drive it correctly.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate, but it only names 3 of 14 parameters (OrderNumber, ItemNumber, CustomerNumber) and trails off with "etc." The eleven remaining parameters — page, skip, pageSize, fields, distinct, division, Location, OrderType, historic, countOnly, totalCount — are documented nowhere, so the agent has no basis for using them.

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 names a specific verb and resource ("Find Customer Order Lines"), which clearly separates it from the create/update/delete siblings on the same resource. It does not, however, distinguish it from customer_order_lines_get, so the find-vs-get boundary is left to the agent to infer.

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 explicit when-to-use guidance: nothing says when to prefer this over customer_order_lines_get, whether filters are optional or combinable, or what happens when no filter is supplied. "Filter by ... etc." gestures at usage but leaves the agent to guess.

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