Skip to main content
Glama

Sap St22 Lookup

sap_st22_lookup
Read-only

Lists SAP ST22 ABAP short dumps for a selected date, then reads a specific runtime error's details by index. Use it to retrieve structured short-dump data instead of running the ST22 transaction.

Instructions

Look up ABAP short dumps (runtime errors) from ST22. If sap-adt is available, prefer its list_short_dumps/get_short_dump_details tools. USE THIS instead of sap_transaction('ST22') - faster and returns structured data. Two-step workflow: call once without dump_index to list dumps, then call again with dump_index=N to read a specific dump's detail. By default lists today's dumps. Use date parameter for other dates.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sap_st22_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDate to search (YYYY-MM-DD). Default: today. Uses Today/Yesterday toolbar buttons when applicable.
sessionNoSession ID (e.g., "s1", "s2"). None uses primary session.
agent_idNoAgent identifier for binding check. Optional.
dump_indexNoSelect the Nth dump from the list (0-based) to read detail. If None, returns the dump list only.
output_fileNoIf provided, write results to this JSON file (on success only).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/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 the safety profile is covered; the description adds value beyond that by disclosing the structured two-step interaction model, the default scope (today's dumps), and the comparative behavior against sap_transaction. It stops short of describing failure modes (e.g., an out-of-range dump_index) or how results are shaped, but with annotations carrying the safety burden this is solid.

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?

Front-loaded with the verb and resource, then routing guidance, then the workflow, then the default scope. Every sentence carries distinct operational information; no filler or restatement of the title.

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 annotations and an output schema present, the description need not explain return values, and it covers selection, workflow, and default scope adequately. Minor gaps remain around error/edge behavior (stale or out-of-range dump_index, session binding) for a tool that drives a GUI session.

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

Parameters4/5

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

Schema coverage is 100%, so baseline would be 3, but the description adds real meaning by framing dump_index as a mode switch tied to a call sequence ("call once without dump_index to list dumps, then call again with dump_index=N"), which is workflow semantics the per-field schema text does not convey. It also reinforces the default date scope, though it says nothing about session or output_file behavior.

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?

Names a specific verb and resource ("Look up ABAP short dumps (runtime errors) from ST22") and explicitly distinguishes itself from two named alternatives, sap-adt's list_short_dumps/get_short_dump_details and sap_transaction('ST22'). An agent can pick this tool over its siblings without opening any 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?

Gives explicit when-to-use (prefer sap-adt if available), an explicit alternative with a stated advantage ("USE THIS instead of sap_transaction('ST22') - faster and returns structured data"), and the exact call sequence for the two-step workflow. Nothing about tool selection is left to inference.

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