Skip to main content
Glama

Sap Select Tab

sap_select_tab

Selects a tab on the current SAP screen by its label text, enabling navigation to specific tab content; optionally targets a named session.

Instructions

Select a tab on the current SAP screen by its label text.

Use sap_get_screen_text to see available tab labels on the current screen.

Args:

  • label: Tab label text (e.g., 'Address', 'Details', 'Allgemeine Daten')

Session parameter:

  • session=None (default): Uses primary session ("s1")

  • session="s2": Targets specific session

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": {
      "label": "<label>"
    },
    "name": "sap_select_tab"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelYes
sessionNo
agent_idNo

Output Schema

NameRequiredDescriptionDefault
errorNoError message if success=False
labelYesTab label that was selected
popupNoPresent when a popup dialog is active on screen
successNoWhether the operation succeeded
active_windowNoWhich window was operated on (e.g., 'wnd[0]', 'wnd[1]'). If 'wnd[1]' or higher, a modal dialog is open.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and openWorldHint=false, so the agent knows this is not a read-only operation. The description adds session-targeting behavior, which is useful context, but it does not explain side effects, error handling, or what happens if the label is not found.

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?

The description is front-loaded with purpose, then discovery guidance, then parameter details. It uses compact bullet formatting and includes only useful examples, with no wasted wording.

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

Completeness3/5

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

The tool has three parameters, one of which ('agent_id') is undocumented in both the schema and the description. An output schema exists so return values need not be explained, but the missing parameter and lack of behavioral detail leave gaps for a mutation-adjacent UI action.

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 0%, so the description must compensate. It clearly explains the 'label' and 'session' parameters with examples and default behavior, but the third parameter ('agent_id') is not mentioned at all.

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 specific verb ('Select') and resource ('a tab on the current SAP screen by its label text'), making the tool's function unambiguous. It is easy to distinguish from siblings like sap_click_button or sap_select_dropdown.

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

Usage Guidelines4/5

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

It explicitly directs the agent to use sap_get_screen_text to discover available tab labels before calling this tool. However, it does not state when-not-to-use conditions or compare against other selection tools.

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