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

abap-config-mcp

by netweaver1970
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Analyze Runtime Dump

analyze_dump
Read-onlyIdempotent

Lists ABAP runtime dumps from SAP with category, short text, ID and user so you can locate a failing run after tests or program execution and open it in ST22.

Instructions

List ABAP runtime dumps (the short dumps shown in ST22) from the SAP system: category, short text, dump id and user. Lists them only; it does not return the dump text or stack. Use it to find a failing run after abap_run_class or run_unit_tests, then open the dump in ST22. Read-only; the optional query narrows the feed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "analyze_dump"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoFree-text filter passed to the ADT dump feed; omit to list the dumps ADT returns by default
connectionIdNoSAP system connection ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.16.2
    • changedInput schema / properties / query / description
      Previous value: -"Optional search filter"New value: +"Free-text filter passed to the ADT dump feed; omit to list the dumps ADT returns by default"
  2. First observedv1.16.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety is covered; the description adds genuine scope information beyond that by stating it returns only feed metadata and not dump text or stack. It also explains that the query narrows the feed rather than replacing it. Pagination or result-size limits for the feed are not disclosed, which keeps it from a 5.

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?

Content is front-loaded: identity and returned fields first, then the limitation, then the intended workflow. Every sentence carries signal, though 'Read-only' is redundant with readOnlyHint=true and the ST22 reference appears twice.

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?

With no output schema, the description correctly compensates by listing the returned fields and explicitly excluding dump text and stack, which is the main ambiguity for a tool named 'analyze_dump'. What remains unstated is the result volume or ordering of the feed, which matters for a list-style tool with no required parameters.

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 both parameters are already documented, including the free-text query and omit-for-default behavior. The description's 'the optional query narrows the feed' largely restates the schema, adding only the framing that this is a narrowing filter rather than a search. Baseline 3 is appropriate.

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?

Uses a specific verb and resource ('List ABAP runtime dumps') and immediately anchors it to a known artifact ('the short dumps shown in ST22'). It also enumerates the fields returned (category, short text, dump id, user), so an agent can distinguish this from diagnostic siblings like abap_memory_report or the run tools without opening the schema.

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

Usage Guidelines5/5

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

Gives an explicit workflow: use it after abap_run_class or run_unit_tests to find a failing run, then open the dump in ST22. It also states the negative case clearly ('lists them only; it does not return the dump text or stack'), so the agent knows when this tool is insufficient rather than over-calling it.

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