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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetBehaviorImplementation

Reads the source code or ADT metadata (package, owner, description) of a named RAP behavior implementation, including active or inactive versions, for ABAP development inspection.

Instructions

[read-only] Reads the RAP behavior implementation (its class) named by behavior_implementation_name in one request: its source code (part "source", the default; active or inactive version) or its ADT metadata document (part "metadata": package, responsible, description). Returns the part read. 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": {
      "behavior_implementation_name": "<behavior_implementation_name>"
    },
    "name": "GetBehaviorImplementation"
  }
}

Input Schema

NameRequiredDescriptionDefault
partNoThe document to read: "source" (default) the source code, "metadata" the ADT metadata document (package, responsible, description, ...).source
versionNoVersion of the source: "active" (default) for the deployed version, "inactive" for the modified version awaiting activation.active
behavior_implementation_nameYesBehaviorImplementation name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv20.1.0
    • addedInput schema / properties / part
      Added value: +{
+  "default": "source",
+  "description": "The document to read: \"source\" (default) the source code, \"metadata\" the ADT metadata document (package, responsible, description, ...).",
+  "enum": [
+    "source",
+    "metadata"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / version / description
      Previous value: -"Version to read: \"active\" (default) for deployed version, \"inactive\" for modified but not activated version."New value: +"Version of the source: \"active\" (default) for the deployed version, \"inactive\" for the modified version awaiting activation."
  2. Changed1 schema field changedv16.0.0
    • changedInput schema / properties / behavior_implementation_name / description
      Previous value: -"BehaviorImplementation name (e.g., Z_MY_BEHAVIORIMPLEMENTATION)."New value: +"BehaviorImplementation name."
  3. First observed

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 carries the full burden and largely meets it: it declares [read-only], explains that the answer is the part read, and discloses the non-obvious batch-mode recording behavior (empty content, answer retrieved by number after the batch). It omits error/not-found behavior and whether inactive reads require the object to be locked, so not 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?

Front-loads the read-only marker and resource before the mode options, and every clause carries content. The single long multi-clause sentence is slightly run-on but not padded.

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 stating what is returned ('Returns the part read') plus the batch-mode return semantics. For a three-parameter read tool this is nearly sufficient; only error and permission behavior are absent.

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% and both enums are already documented in the schema, so the description's restatement of part values and the default adds little beyond the structured fields. Baseline 3 applies when the schema does the heavy lifting.

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 and resource: reads the RAP behavior implementation class named by behavior_implementation_name, and enumerates the two read modes (source, metadata). The resource is distinct enough from GetBehaviorDefinition and UpdateBehaviorImplementation, though the description never explicitly contrasts them.

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?

Implied usage is clear from the part/version enumeration and the batch-mode note, but there is no explicit when-to-use versus alternatives (e.g., version-source siblings for historical versions, or GetBehaviorDefinition for the definition itself). The agent must infer routing from the sibling list.

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