Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

purchase_orders_find

Locate purchase orders in Macola 10 by filtering on status, vendor, division, order number, or buyer planner, with paging and field selection to return only the records you need.

Instructions

Find 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": "purchase_orders_find"
  }
}

Input Schema

NameRequiredDescriptionDefault
TypeNo
pageNo
skipNo
orderNo
StatusNo
fieldsNo
distinctNo
divisionNo
pageSizeNo
countOnlyNo
totalCountNo
OrderNumberNo
BuyerPlannerNo
VendorNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

D1.8/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the entire burden of behavioral disclosure and delivers none: nothing about pagination (despite page/skip/pageSize params), result ordering, countOnly/totalCount side effects, or what the response contains. For a 14-parameter query tool this is a complete gap.

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 wastes no words, but at this length "concise" is really under-specification rather than efficiency. Nothing is front-loaded because nothing is provided.

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?

A 14-parameter search tool with no annotations, no output schema, and no parameter documentation needs a substantial description to be callable correctly. This one leaves the agent guessing about filters, paging, and return shape.

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?

Schema description coverage is 0%, so all 14 parameters (Type, Status, division, OrderNumber, BuyerPlanner, VendorNumber, fields, distinct, countOnly, etc.) are undocumented in both schema and description. The description says nothing about what any of them mean, what format they expect, or which combinations are meaningful.

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

Purpose3/5

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

"Find Purchase Orders" names a verb and a resource, so the agent knows the tool retrieves purchase order records. However, it does nothing to distinguish itself from sibling purchase_orders_get or the other *_find tools, and gives no sense of whether it returns a list, a search result, or a single record.

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 when-to-use guidance, no mention of when to prefer purchase_orders_get over this tool, and no note about required filters or prerequisites. The agent must infer everything 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