Log Feedback
log_feedbackReport technical feedback on SAP GUI automation tool usage, friction points, or optimization opportunities to surface blockers and workflow improvements for tracking and fixes.
Instructions
Log technical feedback about tool usage patterns, friction points, or optimization opportunities. ENCOURAGED whenever you notice something that could improve tooling. If GITHUB_PAT configured, auto-posts as GitHub issue. BE DETAILED: include transaction code, steps to reproduce, tool names, selectors, timing observations, what you tried, error messages. TAGS: 'tool-combination' (tools always used together), 'repetition' (same tool repeated), 'selector' (hard to find), 'timing' (slow/timeout), 'workflow' (could be simplified), 'missing-tool', 'error-handling', 'deadlock' (got stuck), 'problem' (blocked progress). Use markdown formatting: backticks for code, bold for emphasis.
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": {
"feedback": "<feedback>"
},
"name": "log_feedback"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tags | No | ||
| feedback | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| error | No | Error message if success=False | |
| popup | No | Present when a popup dialog is active on screen | |
| logged | Yes | Whether the entry was recorded | |
| success | No | Whether the operation succeeded | |
| entry_id | No | UUID of the entry | |
| issue_url | No | URL of the created GitHub issue | |
| session_id | No | Session ID for resource access | |
| issue_error | No | Error message if issue creation failed | |
| active_window | No | Which window was operated on (e.g., 'wnd[0]', 'wnd[1]'). If 'wnd[1]' or higher, a modal dialog is open. | |
| issue_created | No | Whether a GitHub issue was created from buffered feedback |