Skip to main content
Glama
SAP B1 Briefing MCP Server

SAP B1 Briefing MCP Server

get_followup_suggestions

Generate follow-up talking points for a customer visit by combining overdue invoices, open orders, and previously ordered items to answer 'what should I follow up on' questions.

Instructions

Generate heuristic follow-up talking points for a customer visit: combines overdue invoices, open orders, and previously-ordered items. Intended for 'what should I follow up on' style questions.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses that output is heuristic (i.e. derived, not authoritative) and enumerates the inputs it combines, but it never says whether the call is read-only, whether it mutates anything, or what shape the returned talking points take.

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 sentences, no filler, and the core action and its aggregation scope are front-loaded ahead of the usage hint. Every clause contributes information.

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

Completeness4/5

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

No output schema exists, so the description must convey what comes back; it does so at a high level (follow-up talking points derived from three data categories). It lacks any note on ordering, volume, or determinism of those suggestions, which would matter for an agent deciding whether to trust and present them.

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 coverage is 100% and the cardCode parameter is already documented, including the pointer to find_business_partner, so the schema does the heavy lifting. The description adds only the notion of a "customer visit" scoping, which implies but does not confirm the single-cardCode semantics.

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 gives a specific verb and artifact ("generate heuristic follow-up talking points") plus the data sources it aggregates (overdue invoices, open orders, prior items), which distinguishes it from the raw-data siblings like get_open_overdue_invoices. It stops short of naming a sibling or stating an explicit contrast, so a 4 rather than a 5.

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 states a clear usage trigger: "Intended for 'what should I follow up on' style questions." That is enough context to select the tool over the component siblings, but there are no exclusions or stated preconditions (e.g. that find_business_partner must supply the cardCode first).

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