wals.pro AI 4 weclapp

Preview stock operation

preview_stock_operation

Read-onlyIdempotent

Preview warehouse stock movements, transport orders and internal deliveries, issuing one approval token.

Per-operation required parameters:

movement — documentless booking. kind + article_id or article_number + quantity (omit for serial-tracked) + places: INCOMING_WITHOUT_REFERENCE -> target_storage_place_id; OUTGOING_WITHOUT_REFERENCE -> source_storage_place_id; DIRECT_TRANSFER (same warehouse) -> source + destination storage place. Tracked stock: serial_numbers / batch_number; optional batch_expiration_date, valuation_price, movement_note.
internal_delivery — warehouse-to-warehouse via INTERNAL shipment (the only cross-warehouse channel). mode (CREATE_ONLY | COMPLETE_NOW) + source/destination_warehouse_id + items.
transport_order — same-warehouse pick/transit/put-down (Transportauftrag). mode (CREATE_ONLY | COMPLETE_NOW | RESUME); RESUME needs transportation_order_id, create modes destination_storage_place_id + items (each with source_storage_place_id); optional loading-equipment pair.

Args: operation: movement, internal_delivery or transport_order; foreign parameters are rejected. items: {article_id/article_number, quantity (omit for serial articles), source_storage_place_id?, batch_number?, serial_numbers?}.

Full semantics: get_schema(entity="warehouseStockMovement", detail="payload_guide"). Receipts: preview_entity_action purchaseOrder.bookIncomingGoods. Customer shipments: salesOrder.createShipment.

Returns plan + approval + 'execution', or diagnostics (ready_for_write=false).

when_to_use: corrections, found/lost stock, scrapping, seeding, relocations, inter-warehouse deliveries; after the user explicitly confirms, execute_approved. preconditions: STORABLE articles; exact serial/batch identity; stock available at the source. post_effects: no ERP mutation; the token binds the plan and live stock baseline — drift forces a fresh preview.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`kind`	No
`mode`	No
`items`	No
`quantity`	No
`operation`	Yes
`article_id`	No
`batch_number`	No
`movement_note`	No
`article_number`	No
`correlation_id`	No
`serial_numbers`	No
`valuation_price`	No
`source_warehouse_id`	No
`batch_expiration_date`	No
`source_storage_place_id`	No
`target_storage_place_id`	No
`transportation_order_id`	No
`destination_warehouse_id`	No
`destination_storage_place_id`	No
`loading_equipment_article_id`	No
`loading_equipment_identifier_id`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 25, 2026

TDQS

A5/5.0

Behavior5/5

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

Beyond the readOnlyHint, idempotentHint, and destructiveHint annotations, the description discloses post-effects ('no ERP mutation') and the token-drift behavior ('the token binds the plan and live stock baseline — drift forces a fresh preview'). It also states the return shape ('plan + approval + execution, or diagnostics') even though an output schema exists.

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?

The description is long but justified for a complex 21-parameter operation. It is front-loaded with purpose and per-operation parameter rules, then moves through args, returns, when-to-use, preconditions, and post-effects in a scannable structure.

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

Completeness5/5

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

Despite an output schema and annotations already covering safety, the description adds operational context an agent needs: preconditions, post-effects, token staleness behavior, and pointers to related tools. Nothing material for correct invocation appears missing.

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

Parameters5/5

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

With 21 parameters and 0% schema description coverage, the description compensates thoroughly by documenting per-operation required parameters, their conditional fields, and when to omit fields such as quantity for serial-tracked articles. It explains foreign parameter rejection and routes to get_schema for full payload semantics.

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 states a specific verb and scope: 'Preview warehouse stock movements, transport orders and internal deliveries, issuing one approval token.' It clearly distinguishes this preview tool from the downstream execute_approved action and from adjacent preview tools.

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

Usage Guidelines5/5

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

It gives explicit when_to_use scenarios (corrections, found/lost stock, scrapping, seeding, relocations, inter-warehouse deliveries) and the routing condition: after explicit user confirmation, use execute_approved. It also names alternatives for receipts and customer shipments, so the agent can select the right tool without inference.

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

All wals.pro AI 4 weclapp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?