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_ar_aging

Buckets open AR invoices into overdue ranges (Current, 1-30, 31-60, 61-90, 90+) to reveal receivables aging. Specify an as-of date for an optional snapshot.

Instructions

AR aging report — buckets open AR invoices by overdue days (Current, 1-30, 31-60, 61-90, 90+).

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

Input Schema

NameRequiredDescriptionDefault
asOfDateNoYYYY-MM-DD, defaults to today

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden. It clearly signals a read-only reporting operation and defines the output categories (Current, 1-30, 31-60, 61-90, 90+), which is strong context. It does not explicitly state side-effect-free behavior, but the report wording makes that evident.

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?

A single, front-loaded sentence that identifies the report, the underlying data, and the exact buckets. Every element carries meaning and there is no filler.

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?

The tool has one optional parameter covered fully by the schema, and the description explains what the report contains and how the buckets are structured. For a simple read-only report, nothing essential 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 description coverage is 100%, so the schema already documents asOfDate's format and default. The description adds no additional parameter meaning, matching the baseline for high schema coverage.

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 resource (open AR invoices) and a specific action (bucketing by overdue days). The AR vs AP wording clearly distinguishes it from get_ap_aging and other report tools.

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?

No guidance is given on when to use this tool versus alternatives like get_ap_aging or get_collections_worklist. The intended context is clear from the name, but the description never states exclusions or alternative conditions.

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