Skip to main content
Glama
bfernandez2-seidor

ccv2-logs-mcp

search_logs

Search SAP Commerce Cloud runtime logs by environment, time range, level, aspect, or free-text query. Returns newest-first log entries with timestamp, level, and message.

Instructions

Search SAP Commerce Cloud (CCv2) runtime logs in SAP Cloud Logging. Returns newest-first log lines with timestamp, level, aspect, container, logger and message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoEnd of time range (ISO date or date math)now
envYesTarget environment, e.g. s1 or p2 (must have CCV2_LOGS_HOST_<ENV> configured)
fromNoStart of time range (ISO date or date math like now-1h)now-1h
levelNoLog level filter: ERROR, WARN, INFO or DEBUG
limitNoMaximum number of log lines to return
queryNoFree-text query (simple_query_string over message and logger name)
aspectNoPlatform aspect filter: accstorefront, backoffice, backgroundProcessing or api
offsetNoNumber of matching log lines to skip, for pagination (offset+limit is capped at 10000)
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must carry behavioral burden. It mentions the newest-first ordering but not whether the operation is read-only, what happens on errors, or rate limits. The schema indicates no destructive side effects, but the description could be more explicit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences cover the main points without extraneous information. The description is front-loaded with the action and resource.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 8 parameters and no output schema, the description adequately conveys the purpose and key output fields. It lacks details on pagination and time range syntax, but the schema covers parameters thoroughly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so parameters are well-documented in the schema. The description adds no extra meaning to the parameters beyond listing output fields, which is unrelated.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool searches runtime logs in SAP CCv2 Cloud Logging, specifies the output format (newest-first log lines with specific fields), and uniquely identifies the resource and verb.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives. Since there are no sibling tools, the absence is less critical, but some hints on typical use cases or limitations would improve it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bfernandez2-seidor/ccv2-logs-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server