Skip to main content
Glama

Sap Lookup Fields

sap_lookup_fields

Look up pre-discovered CSS field selectors for an SAP transaction in WebGUI. Returns selectors from a static registry so agents can locate and fill fields without rediscovering them.

Instructions

Look up known field CSS selectors for an SAP transaction (WebGUI only). Returns pre-discovered selectors from a static registry. On Desktop, use sap_discover_fields instead — it discovers fields dynamically.

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": {
      "transaction": "<transaction>"
    },
    "name": "sap_lookup_fields"
  }
}

Input Schema

NameRequiredDescriptionDefault
transactionYesTransaction code (e.g., SE16, VA01, BP)

Output Schema

NameRequiredDescriptionDefault
errorNoError message if success=False
popupNoPresent when a popup dialog is active on screen
fieldsNoField name → selector
successNoWhether the operation succeeded
transactionYesTransaction code looked up
active_windowNoWhich window was operated on (e.g., 'wnd[0]', 'wnd[1]'). If 'wnd[1]' or higher, a modal dialog is open.
similar_transactionsNoSimilar tcodes if not found

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the key trait that results come from a static, pre-discovered registry (implying possible staleness or incomplete coverage versus dynamic discovery), but says nothing about what happens for an unknown or unsupported transaction code, nor whether the call is side-effect free.

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?

Three short sentences with the environment constraint front-loaded and the alternative routing last. No filler, and the most decision-relevant constraint (WebGUI only) appears in the first sentence.

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 present, the description need not explain return values, and the single documented parameter is covered by the schema. What is missing is what a caller should do when the static registry has no selectors for a transaction, which matters because that is the tool's most likely failure mode.

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% and the single parameter already documents the transaction code with examples (SE16, VA01, BP). The description adds no format or matching guidance (exact code vs prefix, case sensitivity) beyond the schema, so the baseline applies.

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 known field CSS selectors for an SAP transaction") and immediately bounds the scope to WebGUI. It also names the sibling tool it is not (sap_discover_fields), so an agent can distinguish lookup from discovery 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?

Explicitly gives the routing condition: use this on WebGUI, and use sap_discover_fields on Desktop because that one discovers fields dynamically. Both the when and the when-not are stated, along with the alternative by name.

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