Skip to main content
Glama
aytacmehmet

sap-cloud-erp-mcp

by aytacmehmet

Create Purchase Order

s4_purchase_order_create
Destructive

Create purchase orders with required company code, supplier, purchasing organization, group, and items; optionally assign items to sales orders via account assignment.

Instructions

Create a purchase order with at least one item. Required header: companyCode, purchaseOrderType, supplier, purchasingOrganization, purchasingGroup. Required per item: plant, material, orderQuantity, netPriceAmount. For account-assigned items (e.g. category 'M' individual PO tied to a sales order), set item.accountAssignmentCategory and item.accountAssignment {salesOrder, salesOrderItem} — this creates a PurchaseOrderAccountAssignment record.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYesPurchase order items
supplierYesSupplier/vendor number
companyCodeYesCompany code, e.g. '1010'
purchasingGroupYesPurchasing group, e.g. '001'
additionalFieldsNoExtra header fields merged into the request body as-is
purchaseOrderTypeYesPO type, e.g. 'NB'
purchasingOrganizationYesPurchasing organization, e.g. '1010'
Behavior3/5

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the description is consistent. It adds context about the creation of an account assignment record but does not disclose additional behavioral traits like authorization needs or rate limits.

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 description is structured logically with two paragraphs, front-loading the core purpose and required fields. It is concise enough while covering necessary details, though slightly verbose on account assignment.

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?

Given the tool's complexity (7 parameters, nested objects, no output schema), the description adequately covers required fields and special cases like account-assigned items. It does not cover error handling or return values, but that is acceptable for a creation tool without output schema.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage, the baseline is 3. The description adds value by explaining the required relationships (e.g., accountAssignmentCategory must be set for accountAssignment objects) and providing defaults (netPriceQuantity). This goes beyond the schema descriptions.

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 clearly states 'Create a purchase order with at least one item' and lists the required header and item fields. This is a specific verb-resource pair that distinguishes it from sibling tools like update or get.

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 provides explicit required fields and special instructions for account-assigned items. While it does not explicitly state when not to use this tool or compare to alternatives, the name and context signals (sibling tools) make the usage context clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aytacmehmet/sap-cloud-erp-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server