Skip to main content
Glama
Sign In
mcp-abap-adt

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

RuntimeGetDumpById

Read an ABAP runtime dump by ID or URI to retrieve a summary of the runtime error, exception, terminated program, user, time, and termination position, plus the parsed dump.

Instructions

[read-only] [runtime] Read an ABAP runtime dump by its dump_id or URI. Answers a summary — runtime error, exception, terminated program, time, user, and the source position where it terminated — and the parsed dump. Recordable: in batch mode a call is recorded under the next number and answers with empty content; its answer is read by number after the batch ends.

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": {
      "dump_id": "<dump_id>"
    },
    "name": "RuntimeGetDumpById"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNoDump view mode: default payload, summary section, or formatted long text.default
dump_idYesThe dump's id, or its URI as a dumps feed entry carries it.
response_modeNoWhat is returned: "payload" — the parsed dump, "summary" — runtime error, exception, terminated program, time, user and termination position, "both" — summary and payload.both

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv16.0.0
    • changedInput schema / properties / dump_id / description
      Previous value: -"Full runtime dump ID (e.g. from RuntimeListFeeds)."New value: +"The dump's id, or its URI as a dumps feed entry carries it."
    • changedInput schema / properties / response_mode / description
      Previous value: -"Controls what is returned: \"payload\" — full parsed dump data, \"summary\" — compact key facts only (title, exception, program, line, user, date…), \"both\" — summary + full payload."New value: +"What is returned: \"payload\" — the parsed dump, \"summary\" — runtime error, exception, terminated program, time, user and termination position, \"both\" — summary and payload."
  2. Changed2 schema fields changedv6.5.1
    • changedInput schema / properties / dump_id / description
      Previous value: -"Runtime dump ID (for example: 694AB694097211F1929806D06D234D38)."New value: +"Full runtime dump ID (e.g. from RuntimeListFeeds)."
    • addedInput schema / properties / response_mode
      Added value: +{
+  "default": "both",
+  "description": "Controls what is returned: \"payload\" — full parsed dump data, \"summary\" — compact key facts only (title, exception, program, line, user, date…), \"both\" — summary + full payload.",
+  "enum": [
+    "payload",
+    "summary",
+    "both"
+  ],
+  "type": "string"
+}
  3. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations provided, the description must carry the behavioral burden, and it does: it declares the tool read-only, specifies the answer contents (summary fields plus parsed dump), and discloses the non-obvious batch-mode recording behavior where calls answer empty and are retrieved by number later. It stops short of documenting pagination or size limits for large dumps.

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 front-loaded with the core action and resource, followed by the answer contents and then the batch-mode special case. It is dense but every sentence carries information; the batch-mode sentence is long but earns its place by preventing a subtle misuse.

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 three well-documented parameters, no output schema, and no annotations, the description is nearly complete: it explains the return contents and the batch-mode side effect. It could have mentioned how the 'view' modes affect output, but that is already covered by the schema, so the remaining gap is minor.

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

Parameters3/5

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

Schema description coverage is 100%, so all three parameters (dump_id, view, response_mode) are already documented in the schema. The description reinforces that dump_id accepts an id or URI and implies the summary-vs-payload distinction, but adds no syntax or format detail beyond what the schema provides. Baseline 3 is appropriate.

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 states a specific verb and resource: 'Read an ABAP runtime dump by its dump_id or URI.' It then enumerates what the answer contains, so there is no ambiguity about the tool's function. It does not explicitly contrast itself with runtime siblings (feeds, logs, profiler data), which keeps it at 4 rather than 5.

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?

Usage is implied by the strong purpose statement, and the batch-mode recording note provides operational context. However, the description never says when to use this tool versus alternatives, nor does it state any exclusions or prerequisites (e.g., required authorization for dumps).

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

Deploy Server

Other Tools