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

abap-config-mcp

by netweaver1970
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Run ATC Analysis

run_atc_analysis
Read-onlyIdempotent

Run an ABAP Test Cockpit check on one SAP object and return prioritized ATC findings with check IDs, messages, and line numbers, or a pass result when no issues are found.

Instructions

Run an ABAP Test Cockpit (ATC) check on one object and return each finding as priority, check title and id, message, and object with line number, or a pass message when there are none. Use syntax_check for a quick compile check of unsaved source and run_unit_tests to execute tests. Starts an ATC run on the SAP system for the object; changes no object. Needs ATC authorization and a variant that exists in the system.

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": {
      "url": "<url>"
    },
    "name": "run_atc_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesADT URL of the object to check (e.g. /sap/bc/adt/oo/classes/zcl_order_api, /sap/bc/adt/programs/programs/ZREPORT)
variantNoATC check variant name as configured in the system (default: DEFAULT)
maxResultsNoMaximum findings (default: 100)
connectionIdNoSAP system connection ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.16.2
    • changedInput schema / properties / url / description
      Previous value: -"ADT URL of the object to analyze"New value: +"ADT URL of the object to check (e.g. /sap/bc/adt/oo/classes/zcl_order_api, /sap/bc/adt/programs/programs/ZREPORT)"
    • changedInput schema / properties / variant / description
      Previous value: -"ATC check variant name (default: DEFAULT)"New value: +"ATC check variant name as configured in the system (default: DEFAULT)"
  2. First observedv1.16.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the supplied readOnlyHint/idempotentHint, it discloses that behind the read-only profile an ATC run is actually started on the SAP system, that no object is changed, that ATC authorization is required, and that the variant must already exist. It also compensates for the missing output schema by describing the finding fields and the pass case.

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?

Four tight sentences, front-loaded with the action and result format before alternatives and prerequisites. Slight overlap between "run a check on one object" and "starts an ATC run on the SAP system for the object," though the latter adds the remote-execution nuance.

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

Completeness5/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 still specifies the return payload, the empty-result case, the auth and variant prerequisites, and the read-only contract. An agent has everything needed to decide to call it and to interpret the result.

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 coverage is 100%, so url, variant, maxResults and connectionId are already documented at the schema level. The description adds only the prerequisite that the variant must exist in the system and says nothing about truncation at maxResults.

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?

States a specific verb and resource ("Run an ABAP Test Cockpit (ATC) check on one object") plus the exact return shape (priority, check title and id, message, object with line number, or a pass message). The single-object scope clearly separates it from a broad analysis tool.

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?

Explicitly routes to two alternatives with their conditions: syntax_check for a quick compile check of unsaved source, run_unit_tests to execute tests. This tells the agent when to pick a different tool, not just when to pick this one.

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