Skip to main content
Glama
SAP B1 Briefing MCP Server

SAP B1 Briefing MCP Server

get_open_overdue_invoices

Retrieve a customer's open or overdue accounts receivable invoices by CardCode, including balance due and days overdue, to support sales prep and follow-up.

Instructions

Get a customer's open and/or overdue AR invoices by CardCode, including balance due and days overdue.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cardCode": "<cardCode>"
    },
    "name": "get_open_overdue_invoices"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardCodeYesThe CardCode returned by find_business_partner, e.g. "C20001".
onlyOverdueNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.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 carries the full burden. It is implicitly a read operation, and it usefully discloses what the records contain (balance due, days overdue), but it does not state side effects, paging/row limits, date scope for 'open', currency handling, or whether partially paid or disputed invoices are included.

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 establishes the action, the key, the scope, and the payload with no filler. Nothing is redundant or buried.

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

Completeness3/5

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

For a two-parameter read tool with no output schema and no annotations, the description covers purpose and return contents but leaves the semantics of 'open', the onlyOverdue switch, and result limits to inference. Adequate but with clear gaps.

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 50%: cardCode is fully documented in the schema, while onlyOverdue has no schema description. The phrase 'open and/or overdue' implies that onlyOverdue narrows results to overdue items, but the description never states the default or what the false case returns, so it only partially compensates.

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?

States a specific verb ('Get') and resource ('open and/or overdue AR invoices') plus the lookup key (CardCode) and the notable return fields. It is clearly distinguishable from the sibling tools (sales orders, item availability, partner lookup) by the resource alone, though it never names an alternative explicitly.

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?

Usage is only implied: 'open and/or overdue' hints that the tool can be scoped to overdue-only, and the required cardCode implies a prior partner lookup (the schema, not the description, ties it to find_business_partner). It gives no explicit when-to-use or when-not-to-use guidance relative to the sibling tools.

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