SAP Business One Order-to-Cash MCP Server

create_goods_receipt_po

Record physical receipt of goods into the warehouse by creating a goods receipt PO from an open purchase order. Streamline inventory updates and procurement closure.

Instructions

Create a Goods Receipt PO (GRPO) from an open purchase order — records physical receipt of goods into warehouse.

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": {
      "purchaseOrderDocEntry": "<purchaseOrderDocEntry>"
    },
    "name": "create_goods_receipt_po"
  }
}

Input Schema

Name	Required	Description	Default
`receivedDate`	No	YYYY-MM-DD date goods were received
`purchaseOrderDocEntry`	Yes	DocEntry of the source purchase order

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 26, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It does convey the core effect—recording physical receipt into the warehouse—which goes beyond merely restating the tool name. However, it does not mention side effects such as inventory posting, stock updates, or validation against the purchase order status.

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?

A single sentence that front-loads the action, specifies the source document, and states the operational purpose. Every part earns its place and there is no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a low-complexity tool with only two parameters and no output schema, the description provides sufficient context: it identifies the trigger (open purchase order), the action (goods receipt), and the domain (warehouse receipt). It could add information about required business documents or inventory effects, but the core calling context is adequately covered.

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 100%, so both parameters are already explained in the input schema. The description adds no new parameter-level detail, making the baseline 3 appropriate.

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

Purpose5/5

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

The description uses a specific verb-object pair ('Create a Goods Receipt PO') and clarifies the source ('from an open purchase order') and purpose ('records physical receipt of goods into warehouse'). This clearly distinguishes it from sibling tools like create_purchase_order or create_delivery.

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

Usage Guidelines4/5

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

The description identifies the appropriate condition for use: goods have been physically received against an open purchase order. It does not explicitly name alternatives or state when not to use it, but the context is clear enough for an agent to route correctly among the many procurement-related siblings.

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

Deploy Server