sap-pam
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pam_summaryB | Overview of the SAP Product Availability Matrix data: export date, number of product versions, counts by support status and category, and how many reach end of mainstream maintenance in 3/6/12/24 months. |
| pam_search_productsA | Search SAP product versions in PAM by name (tolerant of shorthand like 'ECC EHP8', 'SolMan 7.2', 'BO 4.3'). Returns support dates, status and a risk assessment. |
| pam_get_productA | Full PAM record for one product version (exact name as in PAM, e.g. 'SAP NETWEAVER 7.5'), including all availability and maintenance dates and the Support Portal link. Suggests close names if not found. |
| pam_expiringA | List SAP product versions whose end of mainstream maintenance falls within the next N months, soonest first. |
| pam_check_landscapeA | Check a list of SAP systems/components (free text, e.g. from a design document or system list) against PAM. Matches each to a product version, rates support risk (critical, high, medium, low or unknown) and gives upgrade options (newer version of the same product, announced versions, SAP's strategic successor). Fuzzy matches should be confirmed by a person. |
| pam_upgrade_optionsA | What to move to from a given SAP product version: the newest released version of the same product with longer mainstream maintenance, any announced (not yet available) version, and SAP's strategic successor product where one exists (e.g. SAP ERP -> SAP S/4HANA). Accepts shorthand like 'ECC6 ehp7' or 'BOBJ 4.3'. |
| pam_changesA | Compare the current PAM export with the previous one: products newly listed or no longer listed, maintenance dates extended or shortened, status changes. Changes that need attention (shortened dates, removed dates, status now in customer-specific/extended/out of maintenance) come first. Optionally focus on a list of systems. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Most tools have clearly distinct purposes (expiring list, summary stats, search, single-record fetch, landscape audit, upgrade paths, changelog). However, pam_search_products and pam_get_product both return product details at different depths, and pam_expiring overlaps conceptually with pam_summary's time-window counts, so a couple of boundaries need care.
All tools share the consistent 'pam_' prefix, which is a strong plus. The second segment mixes noun-style names (pam_summary, pam_changes, pam_upgrade_options) with verb_noun patterns (pam_search_products, pam_get_product, pam_check_landscape), but everything remains readable and predictable.
Seven tools is a well-scoped set for a read-only PAM query surface. Each tool covers a distinct query mode (time-based, aggregate, search, detail, batch audit, upgrades, change diff) and none feels redundant.
The surface covers the key PAM workflows: discovery by name, detail lookup, expiry tracking, summary metrics, landscape auditing, upgrade guidance, and export diffing. A minor gap is the lack of a browse/enumerate tool (e.g. list all products or filter by category/status) without knowing a product name in advance.