Skip to main content
Glama
mcp-erp-server

mcp-erp-server

by aldemarluz

List sales orders

sales_list_orders
Read-only

List sales orders with optional filters for status and customer, and compute order totals from line items. Use it to review, filter, and summarize sales orders in ERP data.

Instructions

List sales orders, optionally filtered by status and customer. Totals are computed from the 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": "sales_list_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
statusNo
customerIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral note - totals are computed from the lines - but says nothing about pagination behavior, default result size, or ordering, which matter for a listing tool with a limit parameter.

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

Conciseness5/5

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

Two short sentences with the core purpose and filter scope front-loaded, and the totals-computation note earns its place. No filler or redundancy.

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 simple read-only list tool with three optional parameters and no output schema, this is minimally adequate. The significant remaining gap is the unaddressed limit/pagination parameter and result ordering, which an agent needs in order to call it well.

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 carry parameter meaning and largely does not. It mentions status and customer filtering but not the five allowed status values or how customerId must be sourced, and it never explains the limit parameter (default 20, max 100) or pagination at all.

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 and resource ('List sales orders') plus filter scope, which clearly separates it from the siblings that deal with customers, prices, order status updates, receivables, and stock. It does not explicitly name or rule out any sibling, so it stops short of a 5.

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

Usage Guidelines3/5

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

The phrase 'optionally filtered by status and customer' implies when the filters are relevant, but gives no when-to-use versus alternatives guidance and no prerequisites. Usage is inferable rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.