Skip to main content
Glama

Log Intent

log_intent

Records the stated purpose and optional context for SAP tasks, especially before write operations, to support compliance and accountability.

Instructions

MANDATORY: Log intent when using SAP. You MUST call this at the start of every SAP task and before any SAP write operation. Required for compliance and accountability. WHEN TO CALL: (1) ALWAYS at the start of every SAP-related user request, (2) ALWAYS before any SAP write operation (create, update, delete, post), (3) At milestones during multi-step workflows (e.g., 'Order 3 of 10'), (4) Before running transactions that modify data. Args: intent = high-level description (e.g., 'User requested to create sales order'), context = optional dict (e.g., {'tcode': 'VA01', 'customer': '12345'}).

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": {
      "intent": "<intent>"
    },
    "name": "log_intent"
  }
}

Input Schema

NameRequiredDescriptionDefault
intentYes
contextNo

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
session_idNoSession ID for resource access
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.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the compliance framing ('required for compliance and accountability') and the timing obligations, which is real context beyond the schema. It never says what actually happens on the call — whether the entry is persisted, whether failure aborts the SAP task, whether skipping it is enforced server-side or merely instructed, or whether repeated calls overwrite anything.

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 key directive, then an enumerated call-timing list, then argument notes — a sensible structure for a frequently-called tool. Some words are redundant (MANDATORY/MUST/ALWAYS repeated across the first two sentences and again in items 1 and 2), which is emphasis rather than information, but the payload stays compact.

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?

For a 2-parameter logging tool with an output schema (so return values need not be explained) and no annotations, the description covers purpose, timing, and both argument shapes adequately. The remaining gap is failure/error behavior and the relationship to the sibling logging tool, which an agent would still have to guess.

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 description coverage is 0%, so the description must compensate, and it largely does: 'intent' is defined as a high-level natural-language description with a concrete example, and 'context' is shown as a structured dict with sample keys ('tcode', 'customer'). That is meaningful added meaning over a bare string/object schema. It stops short of saying how keys should be named or how much detail 'intent' should contain.

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 makes clear this is a logging/audit call: it records a high-level 'intent' plus optional structured 'context' at the start of and during SAP tasks. The verb+resource are stated concretely enough that an agent knows what it does. It does not distinguish itself from the sibling 'log_feedback', which is the one plausible point of confusion an agent would have.

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?

Unusually strong when-to-use guidance: four numbered triggers covering task start, before any write (create/update/delete/post), milestones in multi-step workflows, and before data-modifying transactions. What is missing is the inverse — when this is unnecessary (e.g., read-only browser steps) and how it differs from 'log_feedback'. Per the rubric, clear context without exclusions is a 4.

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