SAP Business One Order-to-Cash MCP Server

get_item_group_sales

Retrieve sales performance by item group or category for a specified date range. Use this to analyze which product categories drive revenue and identify trends.

Instructions

Sales performance by item group/category — uses SMLSVC POST.

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

Input Schema

Name	Required	Description	Default
`toDate`	No
`fromDate`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 26, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'uses SMLSVC POST,' which reveals transport but not whether the operation is read-only, whether it has side effects, what it returns, or any rate-limit/auth concerns. This is insufficient for an agent to understand the call's behavior.

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 very short and front-loaded with the essential purpose. The only slightly questionable addition is 'uses SMLSVC POST,' but it does not make the description bloated.

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?

With no output schema, no annotations, and no parameter guidance, this description is underspecified for confident invocation. An agent can guess that two dates are involved, but it cannot tell what granularity/aggregation, what item-group data is returned, or how this call differs from other sales-analysis tools.

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

Parameters1/5

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

Schema description coverage is 0%, so the description must compensate by explaining the date parameters, but it says nothing about toDate/fromDate, their meaning, range behavior, or optionality. The description adds no parameter semantics whatsoever.

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

Purpose4/5

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

The description names the specific metric ('Sales performance') and the grouping dimension ('item group/category'), so an agent can tell this from sales-period or salesperson tools. It lacks an explicit verb like 'get' or 'returns', but the tool name and phrasing are clear enough.

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

Usage Guidelines2/5

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

There is no guidance about when to use this tool versus any of the many sales-analysis siblings such as get_sales_by_period, get_warehouse_sales, or get_salesperson_performance. The resource name implies a use case, but no explicit context or alternatives are provided.

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

Deploy Server