Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

customer_orders_find

Find customer orders by CustomerNumber, OrderType, Status, date, division, salesperson, or order number, with paging and field selection for targeted lookups.

Instructions

Find Customer Orders. Filter by CustomerNumber, OrderType, Status, dates, 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_orders_find"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
skipNo
StatusNo
fieldsNo
distinctNo
divisionNo
historicNo
pageSizeNo
OrderTypeNo
countOnlyNo
totalCountNo
OrderNumberNo
CustomerNumberNo
SalespersonNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It says nothing about read-only nature, pagination defaults, count semantics, or what historic toggling does, despite pagination-adjacent parameters (page, skip, pageSize) in the schema.

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?

Two short sentences are front-loaded and readable, but 'etc.' is filler that signals incomplete parameter coverage rather than saving space meaningfully.

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?

A 14-parameter search tool with no annotations, no output schema, and no parameter descriptions is under-specified. The description should at minimum explain pagination, count/projection behavior, and the historic flag.

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% across 14 parameters. The description names only CustomerNumber, OrderType, and Status, and then adds 'dates' even though the schema has no date parameter at all. Pagination, projection (fields), aggregation (countOnly, totalCount), division, historic, OrderNumber, and SalespersonNumber are all left undocumented.

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 (Find) and resource (Customer Orders), which is clear enough to distinguish it from create/delete siblings. It does not explicitly distinguish itself from customer_orders_get, but the search framing is evident.

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?

No guidance on when to use this versus customer_orders_get or other find tools. Only an implicit hint that it is a filter-based retrieval, with no exclusions or prerequisites.

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