Skip to main content
Glama
SAP B1 Briefing MCP Server

SAP B1 Briefing MCP Server

get_recent_sales_orders

Retrieve a customer's recent sales orders by CardCode to prepare for visits and follow-ups; use find_business_partner first when only a customer name is available.

Instructions

Get a customer's most recent sales orders by CardCode. Call find_business_partner first if you only have a name.

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

Input Schema

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

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?

No annotations are supplied, so the description must carry the behavioral burden, and 'get' plus 'most recent' imply a read-only, recency-ordered result. However, it does not disclose the silent default window (90 days) or the default row cap (10), both of which materially affect whether an agent misses orders.

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 short sentences, front-loaded with the operation and followed by the one routing caveat. There is no filler and no redundancy.

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 simple three-parameter read tool this covers the core purpose, but with no output schema and no annotations the definition leaves the agent guessing about result shape, ordering direction, and the effect of the default sinceDays/limit values. Adequate but with clear gaps.

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 coverage is only 33%: cardCode is documented in the schema (including its link to find_business_partner), but limit and sinceDays have no description in either place. The description adds nothing about what the limits or the day window mean, so it fails to compensate for the low coverage.

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 states a specific verb and resource ('Get ... sales orders') plus the keying parameter ('by CardCode') and a recency scope ('most recent'). That is enough to separate it from siblings like get_open_overdue_invoices and check_item_availability, though it never explicitly contrasts with them.

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?

It gives a concrete prerequisite and routing rule: 'Call find_business_partner first if you only have a name,' naming the sibling tool and the condition that selects it. It does not state when *not* to use this instead of e.g. the invoices tool, so it stops short of full when/when-not guidance.

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