SAP Business One Order-to-Cash MCP Server

get_warehouse_list

List active warehouses from SAP B1 to get warehouse code, name, and location, helping users choose a valid warehouseCode before creating purchase requests.

Instructions

List active warehouses from SAP B1 (code, name, location). Use this to let the user pick a valid warehouseCode before creating documents like purchase requests.

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

Input Schema

Name	Required	Description	Default
`search`	No	Filter by warehouse code or name (optional)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 26, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it states data source (SAP B1), scope (active warehouses only), and the actual payload fields (code, name, location). It is clearly a read-only list operation, though it does not elaborate on edge behaviors like pagination or result limits.

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?

Two tight sentences: the first states the core function and return fields, the second states when to use it. All words earn their place and key information is front-loaded.

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?

For a simple read/list tool with one optional parameter and no output schema, the description is complete: it tells the agent what data is returned, the source system, the active filter, and the intended use case. Nothing needed to invoke it correctly is missing.

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 coverage is 100%, and the schema already describes 'search' as an optional filter by warehouse code or name. The description reinforces the warehouseCode connection but adds no new parameter-level meaning beyond the schema.

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 ('List') with a clear resource ('active warehouses from SAP B1') and names the returned fields (code, name, location). This distinguishes it from siblings like get_warehouse_sales or get_total_stock, which address different questions.

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 gives a concrete usage context: use it to let the user pick a valid warehouseCode before creating documents like purchase requests. It does not name explicit alternatives or when-not-to-use conditions, but the context is clear enough for an agent to route correctly.

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

Deploy Server