Skip to main content
Glama

SAPDiagnose

Run syntax checks, unit tests, and ATC checks on ABAP objects. Analyze runtime errors, SQL traces, and slow OData calls to diagnose SAP system issues.

Instructions

Run diagnostics on ABAP objects and analyze runtime errors. Actions:

  • "syntax": syntax-check (name+type; optional version; optional source = pre-write dry-run, nothing written).

  • "unittest": run ABAP Unit tests (name+type).

  • "atc": run ATC checks (name+type; optional variant).

  • "cds_testcases": SAP-suggested ABAP Unit test cases for a CDS entity (name; read-only; SAP_BASIS 8.16+).

  • "object_state": compare active and inactive source versions without fetching both (name+type; CLAS compares all includes). Returns ETags, hashes, divergence flags.

  • "quickfix": get quick-fix proposals at a position (name+type+source+line; optional column, sourceUri).

  • "apply_quickfix": apply one proposal, return text deltas, no write (name+type+source+line+proposalUri+proposalUserContent; pass proposalUserContent through exactly, may be empty).

  • "dumps": list/read ST22 short dumps (no id = list; id = read; includeFullText, sections).

  • "traces": list/analyze profiler traces (id+analysis: hitlist=hot spots, statements=call tree, dbAccesses=DB stats).

  • "trace_start": arm a profiler trace for the NEXT matching execution, then reproduce and read via "traces" (write scope; defaults: next HTTP request, SQL on; optional traceUser/processType/maxExecutions/expiresHours/sqlTrace/…).

  • "trace_requests": list armed trace requests. "trace_cancel": cancel one by id (write scope).

  • "system_messages": list SM02 messages. "gateway_errors": list /IWFND/ERROR_LOG (on-prem; detailUrl or id+errorType for detail).

  • "odata_perf": diagnose why an OData call is slow (url = host-relative path from the Network tab); returns the sap-statistics timing split (DB/ABAP/framework/auth) + a verdict. Read-only; needs allowDataPreview.

  • "cds_sql": show the native SQL a CDS view compiles to (name; read-only; may be absent on old releases).

  • "sql_trace_state" / "set_sql_trace_state" (sqlOn; needs SAP_ALLOW_WRITES) / "sql_trace_directory": ST05 SQL-trace control. Quickfix workflow: syntax/ATC → quickfix → apply_quickfix → write via SAPWrite. Full action reference: docs_page SAPDiagnose.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoDump or trace ID (for dumps/traces actions); also the trace-request id to cancel (for trace_cancel). Omit to list, provide to get details.
toNoOptional upper time boundary for feed-based diagnostics actions (system_messages/gateway_errors).
urlNoFor odata_perf: the host-relative OData path to probe, from the Fiori app's Network tab (e.g. "/sap/opu/odata4/sap/.../Entity?$filter=…"). Must be a path on the connected system — absolute URLs are rejected.
fromNoOptional lower time boundary for feed-based diagnostics actions (system_messages/gateway_errors).
lineNoSource line number for quickfix evaluation (required for quickfix/apply_quickfix).
nameNoObject name (for syntax/unittest/atc/object_state); the CDS entity / DDLS source name for cds_testcases and cds_sql
typeNoObject type (PROG, CLAS, etc.) (for syntax/unittest/atc/object_state)
userNoFilter dumps by SAP user (for dumps action)
sqlOnNoFor action="set_sql_trace_state": true to arm the ST05 SQL trace, false to disarm. Combine with user to filter the trace to one SAP user.
actionYesDiagnostic action
columnNoSource column number for quickfix evaluation (default 0 for quickfix actions).
sourceNoCurrent source code (required for quickfix/apply_quickfix).
variantNoATC check variant (for atc action)
versionNoSource version for syntax check (default "active"). Use "inactive" to validate pending changes.
analysisNoTrace analysis type (for traces action with id). hitlist = execution hot spots, statements = call tree, dbAccesses = database access stats.
coverageNoFor action="unittest": also return statement/branch/procedure coverage for the object, plus methodsBelowFull — the methods below 100% statement coverage, worst first (what to test next) — in one extra round-trip. If the coverage endpoint or measurement is unavailable, returns the tests without coverage. Default false.
sectionsNoDump chapter IDs to include for dumps detail mode (for example ["kap0","kap3","kap8"]). Omit to use focused defaults.
sqlTraceNoFor trace_start: capture SQL/DB accesses (default true — required for analysis="dbAccesses").
aggregateNoFor trace_start: aggregate the trace (default true).
detailUrlNoADT detail URL for gateway_errors detail mode (preferred over id+errorType). Accepts absolute or /sap/bc/adt/... path.
errorTypeNoGateway error type for gateway_errors detail by id (for example "Frontend Error"). Required when using id without detailUrl.
sourceUriNoExact ADT source URI for quickfix/apply_quickfix. Defaults to the type/name main source; use this for class includes such as /includes/definitions.
traceUserNoFor trace_start/trace_requests: the SAP user whose matching execution is traced/listed. Defaults to the connected user.
maxResultsNoMaximum results to return for dumps/system_messages/gateway_errors (default 50, bounded to a safe cap).
objectTypeNoFor trace_start: what to match within the process. Defaults to the valid type for the process type (http→url, dialog→transaction, batch→report, rfc→functionModule).
descriptionNoFor trace_start: optional label for the trace request.
processTypeNoFor trace_start: the kind of work process to capture. Default "http" (OData/Gateway). dialog = SAP GUI transaction, batch = background job, rfc = RFC call.
proposalUriNoQuickfix proposal URI from quickfix action (required for apply_quickfix).
expiresHoursNoFor trace_start: hours until the armed request auto-expires (default 24).
maxExecutionsNoFor trace_start: how many matching executions to capture before the request is consumed (default 1).
includeFullTextNoFor dumps detail mode only: include full formattedText blob. Default false to reduce token usage.
proposalUserContentNoOpaque userContent from quickfix action (required for apply_quickfix). May be an empty string; pass through exactly.
proposalAffectedObjectsNoOptional affectedObjects array from quickfix action. Include content for each affected source unit when applying multi-object quickfixes.
Behavior5/5

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

The description goes beyond annotations by labeling actions as read-only ('read-only; no write') and write scope ('write scope'). It discloses behaviors such as 'optional source = pre-write dry-run, nothing written' and 'return text deltas, no write' for apply_quickfix. No contradiction with annotations (readOnlyHint=false, destructiveHint=false).

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?

The description is well-structured with a brief introduction followed by action-specific bullet points. It is front-loaded with the main purpose. However, it is lengthy due to the number of actions; some repetition could be condensed.

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?

Given 33 parameters and no output schema, the description adequately covers the purpose of each action, parameter relevance, and the quickfix workflow. It lacks details on error handling or return formats, but the complexity is handled well overall.

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 100%, so the schema already documents parameters well. The description adds context by grouping parameters under actions and explaining workflow-specific details (e.g., quickfix parameter usage). It adds value beyond schema but is not essential for understanding individual parameters.

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

Purpose5/5

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

The description clearly states 'Run diagnostics on ABAP objects and analyze runtime errors.' It lists all 19 actions with concise explanations, distinguishing this tool from siblings (SAPLint, SAPContext, etc.) by focusing on diagnostics and runtime analysis.

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?

The description provides context for each action and explicitly outlines the quickfix workflow: 'Quickfix workflow: syntax/ATC → quickfix → apply_quickfix → write via SAPWrite.' It also references a documentation page. However, it does not explicitly compare with siblings or state when to avoid the tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/arc-mcp/arc-1'

If you have feedback or need assistance with the MCP directory API, please join our Discord server