Skip to main content
Glama
Sign In
SAP Business One Order-to-Cash MCP Server

SAP Business One Order-to-Cash MCP Server

by parmarnaresh86
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_warehouse_sales

Analyze sales per warehouse over a selected date range. Returns totals grouped by warehouse code to support location-level performance review.

Instructions

Sales breakdown by warehouse — uses SMLSVC POST. Groups by WarehouseCode.

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_sales"
  }
}

Input Schema

NameRequiredDescriptionDefault
toDateNo
fromDateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure. It adds some value by revealing it uses SMLSVC POST and groups by WarehouseCode, but it does not state whether the operation is read-only, what output shape to expect, or how the date parameters affect results.

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 compact and front-loads the core purpose. Both sentences earn their place, and there is no redundant or generic filler.

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

Completeness2/5

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

Despite low complexity, there is no output schema and no annotation coverage. The description omits return-value details, date-range semantics, and any caveats about the SMLSVC POST call, leaving an agent without sufficient context to confidently invoke it correctly.

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 description coverage is 0%, and the description does not mention toDate or fromDate at all. The parameter names and date format are somewhat self-explanatory, but the description fails to compensate for the lack of schema descriptions or clarify date-range behavior.

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?

States a specific resource and operation: 'Sales breakdown by warehouse' and 'Groups by WarehouseCode.' This clearly differentiates it from sibling sales tools like get_sales_by_period or get_item_group_sales on the basis of grouping dimension.

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

Usage Guidelines3/5

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

The description implies usage: an agent should call this when warehouse-level sales breakdown is requested. However, it does not explicitly name alternative tools or conditions for avoiding it, so the routing guidance is only implied.

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

Deploy Server

Other Tools