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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetAbapSemanticAnalysis

Analyze ABAP source code to extract symbols, types, scopes, and dependencies, helping you understand code structure and relationships without batch mode.

Instructions

[read-only] Perform semantic analysis on ABAP code and return symbols, types, scopes, and dependencies. Runs outside batch mode.

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": {
      "code": "<code>"
    },
    "name": "GetAbapSemanticAnalysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesABAP source code to analyze

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv6.11.0
    • removedInput schema / properties / filePath
      Removed value: -{
-  "description": "Optional file path to write the result to",
-  "type": "string"
-}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description does carry the safety signal itself via the '[read-only]' tag and adds a genuinely useful constraint: it cannot run inside batch mode. It does not disclose input size limits, whether the code must be syntactically complete, or what the result looks like beyond a list of categories.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, no redundancy; the read-only marker and the batch-mode caveat are both front-loaded and each sentence carries distinct information.

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?

No output schema exists, and the description compensates by enumerating return categories (symbols, types, scopes, dependencies). The batch-mode restriction is an important operational caveat. What remains unstated is whether the code must be a full compilation unit and any size constraints.

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?

Only one parameter and schema description coverage is 100% ('ABAP source code to analyze'), so the baseline of 4 applies. The description adds nothing parameter-specific, but nothing is missing either.

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?

States a specific verb+resource ('Perform semantic analysis on ABAP code') and names the outputs produced (symbols, types, scopes, dependencies), which distinguishes it from the sibling GetAbapAST (syntax tree) without naming it explicitly. Clear on its own terms, but no explicit sibling differentiation.

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

Usage Guidelines2/5

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

No guidance on when to choose this over GetAbapAST, GetLocalTypes, GetTypeInfo or GetWhereUsed, all of which sit adjacent to it in the sibling list. The only usage-shaped statement is the 'outside batch mode' constraint, which is a restriction rather than a selection rule.

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