Skip to main content
Glama
sap-s4-mcp

sap-s4-mcp

by Inderj1

get_sales_order

Read-only

Retrieves a single sales order from SAP S/4HANA, including all line items, for order details lookup and downstream processing.

Instructions

Get one sales order with its line items.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sales_order": "<sales_order>"
    },
    "name": "get_sales_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
sales_orderYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuine value by disclosing that line items are returned inline, but it says nothing about behavior when the order is missing or about how much related data is included.

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?

A single short sentence, front-loaded with the verb and resource, with zero filler. It is efficient, though its brevity leaves gaps better assessed under completeness rather than verbosity.

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 single-record read with one parameter and no output schema, the listing of returned line items is the key contextual addition. Still missing is the identifier format and any not-found/error behavior, which an agent needs to invoke it reliably.

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 coverage is 0% for the single required parameter, and the description adds no meaning beyond "sales order" — it does not state whether the value is an internal ID, order number, or name, nor any format constraints. With the full burden on the description, this is under-specified.

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 ("Get one sales order") and adds scope detail ("with its line items"). The word "one" implicitly separates it from a list-bulk sibling, so an agent can tell it retrieves a single record rather than a collection.

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, no mention of prerequisites (e.g., needing a known identifier), and no named alternative such as a list/search tool. Usage is only inferable from the singular framing.

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