Skip to main content
Glama

Log Feedback

log_feedback

Report 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

NameRequiredDescriptionDefault
tagsNo
feedbackYes

Output Schema

NameRequiredDescriptionDefault
errorNoError message if success=False
popupNoPresent when a popup dialog is active on screen
loggedYesWhether the entry was recorded
successNoWhether the operation succeeded
entry_idNoUUID of the entry
issue_urlNoURL of the created GitHub issue
session_idNoSession ID for resource access
issue_errorNoError message if issue creation failed
active_windowNoWhich window was operated on (e.g., 'wnd[0]', 'wnd[1]'). If 'wnd[1]' or higher, a modal dialog is open.
issue_createdNoWhether a GitHub issue was created from buffered feedback

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the key side effect: it auto-posts as a GitHub issue when GITHUB_PAT is configured. That conditional external write is exactly the kind of behavior an agent needs to know before calling. It stops short of 5 because it does not say what happens when GITHUB_PAT is absent (local only? silently dropped?) or whether the call can fail on GitHub errors.

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?

Structure is front-loaded and logical: purpose, encouragement, side effect, content requirements, tag vocabulary, formatting hint. The tag glossary is long but each entry earns its place as parameter documentation. A little tightening is possible, but nothing is redundant.

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 need not be explained, and the description covers the two real gaps: what to put in feedback and what each tag means. The remaining omission is the no-GITHUB_PAT path and any failure mode, but for a two-parameter reporting tool this is close to complete.

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 0%, so the description must compensate, and it largely does: it enumerates nine tag values with parenthetical definitions ('tool-combination', 'repetition', 'selector', 'timing', 'workflow', 'missing-tool', 'error-handling', 'deadlock', 'problem') and specifies what the feedback string should contain. It stops short of 5 because it never says whether tags are a closed set (the schema types them as free strings) or what happens with unrecognized tags.

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?

The description leads with a specific verb+resource: 'Log technical feedback about tool usage patterns, friction points, or optimization opportunities,' and enumerates the kinds of content it accepts. It is unambiguous what the tool does, though it never explicitly distinguishes itself from the sibling log_intent tool, so an agent must infer the boundary.

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?

Usage is stated positively and forcefully ('ENCOURAGED whenever you notice something that could improve tooling'), which gives a clear trigger condition. It lacks any when-not-to-use guidance or explicit alternatives, so it falls short of the top score, but the intended usage context is easy to act on.

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