Skip to main content
Glama

RuntimeRunClass

Execute an ABAP class that implements if_oo_adt_classrun and returns execution output; optionally profile the run to capture a performance trace.

Instructions

[runtime] Execute an ABAP class implementing if_oo_adt_classrun and return its output. Set profile=true to also capture a profiler trace (returns profilerId/traceId alongside output).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
class_nameYesABAP class name to execute.
profileNoWhen true, run with the profiler and resolve the resulting traceId. Default false.
descriptionNoProfiler trace description (only used when profile=true).
all_procedural_unitsNo
all_misc_abap_statementsNo
all_internal_table_eventsNo
all_dynpro_eventsNo
aggregateNo
explicit_on_offNo
with_rfc_tracingNo
all_system_kernel_eventsNo
sql_traceNo
all_db_eventsNo
max_size_for_trace_fileNo
amdp_traceNo
max_time_for_tracingNo
max_trace_attemptsNoMax polling attempts to resolve traceId after execution (default 5). Only used when profile=true.
trace_retry_delay_msNoDelay in ms between trace polling attempts (default 2000). Only used when profile=true.
trace_lookup_urisNoAdditional URIs to consult when resolving the trace (advanced, profile=true).
Behavior2/5

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

With no annotations, the description carries the full burden. It mentions output and profiler trace but does not disclose error handling, side effects, or the response format. For a runtime execution tool, this is insufficient.

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 two sentences, front-loaded with the main purpose. It is concise but could be tighter by avoiding repetition of 'profile=true'. Overall, it earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 19 parameters, no output schema, and no annotations, the description is extremely sparse. It does not explain return values, error conditions, or the meaning of most parameters, making it incomplete for a complex tool.

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

Parameters2/5

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

Schema description coverage is only 32%. The description only explains the profile parameter minimally; it does not cover the many other boolean and numeric parameters. The description fails to compensate for the low schema coverage.

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 the tool's purpose: execute an ABAP class implementing if_oo_adt_classrun and return its output. It also explains the optional profiling feature, distinguishing it from the sibling tool RuntimeRunClassWithProfiling by inclusion of the profile parameter.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for running a class with optional profiling but does not explicitly state when to use this tool vs. alternatives like RuntimeRunClassWithProfiling. No guidance on prerequisites or conditions is provided.

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/fr0ster/mcp-abap-adt'

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