Skip to main content
Glama

Sap Se93 Lookup

sap_se93_lookup
Read-only

Retrieve transaction metadata from SAP SE93, including description, program, screen/selection details, and GUI capabilities for one or multiple transaction codes.

Instructions

Look up transaction metadata from SE93 (Transaction Maintenance). USE THIS instead of sap_transaction('SE93') - faster and returns structured data. Returns transaction description, program, screen/selection info, and GUI capabilities. Supports single tcode or list of tcodes. Currently supports 'dialog' and 'report' transaction types.

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": {
      "tcodes": "<tcodes>"
    },
    "name": "sap_se93_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
tcodesYesSingle transaction code or list of codes (e.g., 'VA01' or ['VA01', 'MM01'])
sessionNoSession ID (e.g., "s1", "s2"). None uses primary session.
agent_idNoAgent identifier for binding check. Optional.
output_fileNoIf provided, write full results to this JSON file and return summary. Recommended for >10 transactions to avoid context overflow.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/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 value with the performance/structured-output rationale and the limitation that only 'dialog' and 'report' transaction types are handled, which prevents wasted calls. It does not describe failure behavior for unsupported types, keeping it just below the top mark.

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?

Four short sentences, zero filler, with the imperative routing instruction front-loaded ahead of the return-value and scope details. Every sentence carries distinct information.

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?

Return values need not be explained given an output schema exists, yet the description still summarizes them, and it covers scope limits and batching. The only uncovered angle is what happens on an unsupported transaction type, a minor gap for a read-only lookup.

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 four parameters including the string-or-array union and the output_file spill-to-disk behavior. The description's note about single vs. list input restates what the schema already says, adding no new semantics.

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?

States a specific verb and resource (look up transaction metadata from SE93) and enumerates exactly what is returned: description, program, screen/selection info, GUI capabilities. It also explicitly distinguishes itself from the sibling sap_transaction, so an agent can choose without opening 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?

Gives an explicit routing rule ("USE THIS instead of sap_transaction('SE93')") with the reason (faster, structured), names the accepted input shape (single tcode or list), and declares a hard scope boundary via the supported transaction types. No inference is required.

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