Skip to main content
Glama

Sap Slg1 Lookup

sap_slg1_lookup
Read-only

Search and read SAP application logs (SLG1) with structured metadata like date, user, object, and message count. Provide a log object to filter; use '*' to query all logs.

Instructions

Search and read SAP application logs from SLG1. USE THIS instead of sap_transaction('SLG1') - faster and returns structured data. Returns log entries with metadata (date, time, user, object, subobject, external ID, message count, log number). Best used when the log object is known (e.g., /SDF/CALM for Cloud ALM, /SDF/AIMAX for AI). Use '*' as object to search all logs. Requires at minimum the 'object' parameter. Returns up to 50 logs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "object": "<object>"
    },
    "name": "sap_slg1_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
objectYesLog object (e.g., '/SDF/CALM', '/SDF/AIMAX', '*' for all)
sessionNoSession ID (e.g., "s1", "s2"). None uses primary session.
to_dateNoEnd date filter (YYYY-MM-DD format)
agent_idNoAgent identifier for binding check. Optional.
from_dateNoStart date filter (YYYY-MM-DD format)
subobjectNoLog subobject (optional filter)
external_idNoExternal identifier (optional filter)
output_fileNoIf provided, write results to this JSON file and return summary.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral facts beyond the annotations: relative speed versus sap_transaction and a hard result cap ('Returns up to 50 logs'). The listed metadata fields overlap with the existing output schema, so that sentence adds little.

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

Conciseness4/5

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

Front-loaded with purpose and the sibling comparison, which is exactly the right ordering. The metadata enumeration in parentheses is largely redundant with the output schema and could be dropped without loss.

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?

With an output schema and annotations present, the description covers the remaining gaps an agent needs: result cap, speed advantage, wildcard usage, and required parameter. It doesn't explain the output_file side effect, but the schema documents that parameter, so the omission is minor.

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 description coverage is 100%, so the schema already documents all eight parameters, including the '*' wildcard and date formats. The description only restates the required 'object' parameter and the wildcard, adding no syntax or interaction detail (e.g., how from_date/to_date combine with object) beyond the schema.

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 opens with a specific verb and resource ('Search and read SAP application logs from SLG1') and immediately distinguishes itself from the sibling sap_transaction('SLG1') by naming it as the slower alternative. An agent can select this tool without inspecting either schema.

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

Usage Guidelines5/5

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

It states the preferred alternative explicitly ('USE THIS instead of sap_transaction(\'SLG1\')'), gives the reason (faster, structured data), and adds a situational condition ('Best used when the log object is known'). The wildcard fallback ('Use \'*\' as object to search all logs') covers the case where the object is unknown.

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