SAP Ariba MCP Server
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_event_summaryB | Retrieve supplier bids for a sourcing event. Args: doc_id: Document ID (e.g., 'Doc1213131') user: Username (e.g., myuser) password_adapter: Password adapter (e.g., 'myadaptor') realm: Realm name (e.g., 'myrelm') |
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 1 tool
With only one tool, there is no possibility of confusion or misselection between tools. The single tool's purpose is clearly defined.
The one tool name (get_event_summary) follows a clear verb_noun pattern and is internally consistent. Since there are no other tools, there are no naming inconsistencies.
A single tool is far too few for a server named 'SAP Ariba MCP Server,' which implies a broad procurement/sourcing domain. This is a significant under-provisioning for the apparent scope.
The tool only retrieves supplier bids for a sourcing event. There are no operations for managing events, suppliers, bids, or any other typical lifecycle actions, making the surface severely incomplete for the stated domain.