Skip to main content
Glama

Sap Quick Report

sap_quick_report

Execute SAP report/list transactions by filling selection-screen fields, checkboxes, and radios, pressing F8, then returning results in one call.

Instructions

Execute a transaction, fill the selection screen (fields, checkboxes, radio buttons), press Execute (F8), and return the result — all in one call.

Works with any SAP report/list transaction that has a selection screen (VA05, ME2M, MB51, FBL1N, Z-transactions, etc.).

After execution, you remain on the result screen. If the result is 'unknown', use individual tools to investigate further.

If you already know a transaction shows a popup after F8 (e.g., a variant selection dialog), pass post_f8_keys=['Enter'] to dismiss it automatically.

Do NOT use for:

  • SE16 (use sap_se16_query instead)

  • SM37 (use sap_sm37_lookup instead — has job log support)

  • Transactions without selection screens (e.g., BP, VA01)

  • SE11/SE24/SE37 (use dedicated lookup tools)

WebGUI-only. Returns an error on desktop backend.

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": {
      "tcode": "<tcode>"
    },
    "name": "sap_quick_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
tcodeYesSAP transaction code (e.g., "VA05", "ME2M", "FBL1N").
fieldsNoLabel-value pairs for text fields on the selection screen.
radiosNoLabel-selected pairs for radio buttons on the selection screen.
sessionNoSession ID (e.g., "s1", "s2"). None uses primary session.
agent_idNoAgent ID for multi-agent session binding.
max_rowsNoMaximum rows to read from the result table. Must be >= 1.
checkboxesNoLabel-checked pairs for checkboxes on the selection screen.
output_fileNoIf provided, write the result as JSON to this file path.
post_f8_keysNoKeys to press after F8 to dismiss popups (e.g., ["Enter"]). Max 3 keys. Each key is only pressed if the screen is still unresolved.

Output Schema

NameRequiredDescriptionDefault
errorNoError message if success=False
popupNoPresent when a popup dialog is active on screen
tableNoTable data when screen_type is 'table' or 'list'
tcodeYesTransaction code that was executed
successNoWhether the operation succeeded
warningsNoNon-fatal warnings from the pipeline
page_titleNoScreen title after F8
screen_textNoScreen text when screen_type is 'error' or 'unknown'
screen_typeYesWhat appeared after F8: table, list, empty, error, or unknown
active_windowNoWhich window was operated on (e.g., 'wnd[0]', 'wnd[1]'). If 'wnd[1]' or higher, a modal dialog is open.
status_bar_typeNoStatus bar type if read
status_bar_messageNoStatus bar text if read

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false and openWorldHint=false, so the description carries real weight and delivers: the post-execution state ('you remain on the result screen'), the meaning of an 'unknown' outcome and the fallback to individual tools, automatic popup dismissal via post_f8_keys, and a hard environmental constraint (WebGUI-only, errors on desktop). These are behavioral traits the agent could not infer from the annotations or the schema.

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 one-call workflow, then applicability, then a bulleted exclusion list, then the edge-case tip. Every sentence carries information an agent needs to select or invoke the tool; there is no restatement of the tool name or filler.

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

Completeness5/5

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

An output schema exists, so return values need no prose, and the description still covers the relevant post-call state and the failure/ambiguity path ('unknown'). For a 9-parameter, multi-step automation tool with side effects, nothing an agent needs to call it correctly appears to be missing.

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 description coverage is 100%, so the mechanics of every parameter are already documented; the baseline would be 3. The description pushes slightly past that by giving the practical scenario for post_f8_keys (a known variant-selection dialog) and by framing fields/checkboxes/radios collectively as 'the selection screen', which tells the agent how these parameters relate to one step rather than being independent knobs. It does not explain how labels are matched (exact vs. partial), which is the main remaining semantic gap.

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 states a concrete verb chain and resource: execute a transaction, fill the selection screen, press F8, return the result. It then scopes applicability to 'any SAP report/list transaction that has a selection screen' with concrete examples (VA05, ME2M, MB51, FBL1N, Z-transactions), and names the sibling tools it is not (sap_se16_query, sap_sm37_lookup). An agent can distinguish it from every listed alternative without opening a 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?

There is an explicit 'Do NOT use for' block naming four alternatives and the condition that selects each (SE16, SM37, transactions without selection screens, SE11/SE24/SE37). It also gives an exclusion on backend type ('WebGUI-only. Returns an error on desktop backend') and an escape hatch when the result is 'unknown'. This is the full when / when-not / alternative triad.

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