Skip to main content
Glama
Sign In
MCP SAP GUI Server

MCP SAP GUI Server

by kts982
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Sap Select Checkbox

sap_select_checkbox

Select or deselect a checkbox on the current SAP GUI screen by setting its checkbox ID and selected state. Find GuiCheckBox IDs with screen element discovery before toggling.

Instructions

Select or deselect a checkbox on the current SAP screen.

Set selected=false to uncheck. Use sap_get_screen_elements with type_filter='GuiCheckBox' to find checkbox IDs.

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": {
      "checkbox_id": "<checkbox_id>"
    },
    "name": "sap_select_checkbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
selectedNo
checkbox_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the safety profile is covered structurally. The description adds that the action applies to the 'current SAP screen', implying session/screen-state dependency, but says nothing about whether toggling fires server-side events, whether state persists, or what happens if the ID doesn't exist on screen.

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, front-loaded with the core action, then the deselect trick, then ID discovery. No filler and no repetition of structured fields.

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?

An output schema exists so return values needn't be described, and both parameters are given meaning. What's missing is a brief note on the screen-state precondition (checkbox must exist on the active screen) and error behavior for a bad ID, which matters for an interactive UI-automation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and does so well: it explains the semantics of 'selected' (false = uncheck, implying default true = check) and tells how to obtain a valid 'checkbox_id' with the exact type filter. That is materially beyond what the bare schema provides.

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 ('select or deselect a checkbox') scoped to 'the current SAP screen', which is unambiguous. It doesn't explicitly distinguish itself from the close sibling sap_select_radio_button, which keeps it from a 5.

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?

Gives concrete operational guidance: use selected=false to uncheck, and discover checkbox IDs via sap_get_screen_elements with type_filter='GuiCheckBox'. It names the prerequisite tool and the exact filter, but offers no when-not-to-use condition or mention of the radio-button alternative.

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

Deploy Server

Other Tools