Skip to main content
Glama

Sap Get Shortcuts

sap_get_shortcuts

Discover keyboard shortcuts for the current SAP screen before clicking buttons; returns each action and key combination to support reliable navigation.

Instructions

Discover keyboard shortcuts available on the current SAP screen. Use BEFORE clicking buttons - shortcuts like F5, Ctrl+S are faster and more reliable. Returns action text and key combination for each available shortcut.

Session parameter:

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

  • session="s2": Targets specific session (for parallel agents)

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_get_shortcuts"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionNoSession ID (e.g., "s1", "s2"). None uses primary session.
agent_idNoAgent identifier for binding check. Optional.

Output Schema

NameRequiredDescriptionDefault
errorNoError message if success=False
popupNoPresent when a popup dialog is active on screen
successNoWhether the operation succeeded
shortcutsNoList of keyboard shortcuts available on current screen
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

A4.1/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it does disclose return content ("action text and key combination for each available shortcut") plus the reliability/performance benefit of shortcut use over clicking. It does not state that the call is non-mutating or that discovery leaves screen state unchanged, which for a read-looking tool would have closed the remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose and the key timing rule, then a compact session block. The session block partially restates schema defaults, which is minor redundancy, but no sentence is wasted and the structure is easy to scan.

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?

For a zero-required-parameter read tool with an output schema, the description covers purpose, timing, return shape, and the one non-obvious parameter. Nothing an agent needs in order to invoke it correctly is 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 coverage is 100%, so the baseline would be 3, but the description adds meaning beyond the schema by explaining the default resolution (None maps to primary session "s1") and the intent behind targeting another session ("for parallel agents"). That rationale is not in the schema, which only says the parameter is a session ID.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: "Discover keyboard shortcuts available on the current SAP screen." An agent can tell this apart from action-oriented siblings like sap_press_key or sap_click_button because the description frames it as discovery of available options. It stops short of explicitly naming the sibling it complements, but the purpose is unambiguous.

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?

"Use BEFORE clicking buttons - shortcuts like F5, Ctrl+S are faster and more reliable" gives a concrete timing rule and a reason, which is exactly the guidance an agent needs to prefer this over clicking. It stops short of stating when NOT to use it (e.g., screens with no shortcuts) or naming an explicit alternative tool.

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