Skip to main content
Glama
SAP B1 Briefing MCP Server

SAP B1 Briefing MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LOG_LEVELNoLogging level for the server's stderr-only structured logging. Documented in .env.example; copy it to .env if you need to override the default.
SAP_PASSWORDNoReserved environment variable for a future real SAP Business One Service Layer backend; unused while DATA_PROVIDER=mock.
SAP_USERNAMENoReserved environment variable for a future real SAP Business One Service Layer backend (use a dedicated, least-privilege, read-only integration user); unused while DATA_PROVIDER=mock.
DATA_PROVIDERNoSelects the data backend. `DATA_PROVIDER=mock` is the only implemented backend today.
SAP_COMPANY_DBNoReserved environment variable for a future real SAP Business One Service Layer backend; unused while DATA_PROVIDER=mock.
SAP_SERVICE_LAYER_URLNoReserved environment variable for a future real SAP Business One Service Layer backend; unused while DATA_PROVIDER=mock.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
find_business_partnerA

Search for a business partner (customer or vendor) by name, even if misspelled or only partially remembered. Returns ranked candidate matches rather than a single forced result — use this to disambiguate before calling other tools with a CardCode.

get_recent_sales_ordersA

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

get_open_overdue_invoicesA

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

check_item_availabilityB

Check stock/availability for a product by item code or name (supports fuzzy name search).

get_followup_suggestionsA

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.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a clearly distinct resource and action: business partner lookup, sales orders, AR invoices, item availability, and an aggregate follow-up generator. The only potential overlap is get_followup_suggestions, but its description explicitly frames it as a heuristic summary for 'what should I follow up on' questions, distinguishing it from the raw-data retrieval tools.

Naming Consistency5/5

All five tools use consistent snake_case verb_noun naming (find_business_partner, get_recent_sales_orders, get_open_overdue_invoices, check_item_availability, get_followup_suggestions). The verb variations (find/get/check) are semantically meaningful rather than inconsistent.

Tool Count5/5

Five tools is well-scoped for a customer-visit briefing server, with each tool earning its place by covering a distinct briefing input. There is no filler or redundancy.

Completeness4/5

The surface covers the core briefing workflow: identify the customer, pull recent orders, surface overdue invoices, check item stock, and synthesize follow-ups. Minor gaps exist around customer profile details (contacts, credit status) and order/invoice line-level detail, but these are workable around for the stated briefing purpose.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues