ccv2-logs-mcp
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 |
|---|---|
| search_logsA | Search SAP Commerce Cloud (CCv2) runtime logs in SAP Cloud Logging. Returns newest-first log lines with timestamp, level, aspect, container, logger and message. |
| error_summary | Summarize ERROR-level SAP Commerce Cloud (CCv2) runtime logs by logger over a time range. Always filters on ERROR level (not parameterizable); returns per-logger counts, a per-aspect breakdown and a sample message for each logger. |
| log_context | Retrieve the log lines surrounding an anchor event (identified by timestamp + pod) in SAP Cloud Logging. Returns an anchor-centred, chronologically ordered window scoped to the same pod. Context is positional: if several log lines share the exact anchor timestamp, the tool treats the first one it encounters as the anchor. |
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 ambiguity. The agent will always select search_logs for any log-related task.
Single tool follows a clear verb_noun pattern (search_logs), consistent with MCP conventions.
A single tool for log searching is borderline. While it covers the core function, a typical logging server might benefit from additional tools for listing sources or filtering by context.
The tool provides basic log search but lacks obvious features like log source enumeration, time-range filtering beyond what is implicit, or multi-aspect queries. This may cause agent failures for complex log retrieval tasks.