Skip to main content
Glama
sap-s4-mcp

sap-s4-mcp

by Inderj1

list_sales_orders

Read-only

Retrieve and filter SAP sales orders, newest first, by customer ID and creation date to review recent orders.

Instructions

List sales orders, newest first.

Args: sold_to_party: customer (business partner) id to filter on. created_from: only orders on or after this date (YYYY-MM-DD).

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

Input Schema

NameRequiredDescriptionDefault
topNo
created_fromNo
sold_to_partyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true and openWorldHint=true, so safety is covered, and the description adds the useful behavioral fact that results come newest-first. However it says nothing about how many records come back, whether the result set is truncated by the default limit, or how to page further, which matters for a listing tool whose default is 20.

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?

The summary sentence is front-loaded and the per-argument notes are terse and free of filler. The Args block is a slightly mechanical format but each line earns its place by adding format or entity-type detail absent from the schema.

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 three-parameter read-only listing tool with no output schema, the definition covers identity and two filters but omits the result-size/limit story entirely. An agent can call it correctly, yet cannot reason about pagination or total result volume from this description.

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

Parameters3/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 and it only partly does: it clarifies sold_to_party as a business-partner id and gives the YYYY-MM-DD format for created_from. The third parameter, top, is never mentioned, so the default page size of 20 has no explanation anywhere.

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 gives a specific verb and resource ("List sales orders") plus an ordering guarantee ("newest first"), so an agent immediately knows this is a collection-read tool. It does not explicitly contrast itself with the sibling get_sales_order, but the list-vs-get distinction is clear from the phrasing.

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?

Usage context is only implied: the filters (customer, created-since date) hint at when this tool applies, but there is no statement of when to prefer it over get_sales_order or list_proposals. No exclusions or prerequisites are given, leaving the agent to infer the boundary between listing and fetching a single order.

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