cloud-alm-itsm-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| reporter | Yes | Reporter email for API | |
| cloud_alm_api | Yes | SAP Cloud ALM ITSM API endpoint | |
| cloud_alm_token_endpoint | Yes | OAuth token endpoint for SAP Cloud ALM | |
| cloud_alm_itsm_api_clientid | Yes | Client ID for OAuth 2.0 | |
| cloud_alm_itsm_api_clientsecret | Yes | Client secret for OAuth 2.0 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_installationsC | Retrieve installations from SAP Cloud ALM ITSM API with optional pagination |
| get_installations_by_system_typeB | Filter installations by system type (e.g., BTP, Public Cloud) |
| get_installations_by_customerB | Filter installations by customer number |
| get_installations_by_productA | Filter installations by product name |
| search_installationsA | Search installations by various fields (system name, customer, product, etc.) |
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 5 tools
All five tools are variations of retrieving installations with different filter criteria. get_installations is the base list, while by_system_type, by_customer, by_product, and search_installations overlap heavily, with search_installations effectively covering the same use cases as the others.
Most tools follow a consistent get_installations_by_X pattern, but search_installations deviates by using a different verb. Aside from this one exception, the naming is predictable and readable.
Five tools are dedicated to a single read operation (listing installations) with different filters. This is over-fragmented; a single tool with flexible filter parameters would suffice. The count feels unnecessarily high for the narrow scope.
The server only provides read/filter capabilities for installations. There are no create, update, delete, or lifecycle operations, and the server name suggests a broader ITSM scope that the tools do not cover, leaving significant gaps.