Skip to main content
Glama
fr0ster

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

CreateBehaviorImplementation

Creates an ABAP behavior implementation class for a given behavior definition. Use this to initialize the class before adding implementation code.

Instructions

Create a new ABAP behavior implementation class for a behavior definition. Creates the object in initial state. Use UpdateBehaviorImplementation to set implementation code afterwards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
class_nameYesBehavior Implementation class name (e.g., ZBP_MY_ENTITY). Must follow SAP naming conventions (typically starts with ZBP_ for behavior implementations).
descriptionNoClass description. If not provided, class_name will be used.
package_nameYesPackage name (e.g., ZOK_LOCAL, $TMP for local objects)
transport_requestNoTransport request number (e.g., E19K905635). Required for transportable packages.
behavior_definitionYesBehavior Definition name (e.g., ZI_MY_ENTITY). The behavior definition must exist.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / activate
      Removed value: -{
-  "description": "Activate behavior implementation after creation. Default: true.",
-  "type": "boolean"
-}
    • removedInput schema / properties / implementation_code
      Removed value: -{
-  "description": "Implementation code for the implementations include (optional). Contains the actual behavior implementation methods.",
-  "type": "string"
-}
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

No annotations provided; description adds 'Creates the object in initial state' but does not disclose side effects, permission requirements, activation needs, or validation details. Moderate clarity but leaves gaps.

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 sentences: first states purpose, second provides usage guideline. No filler words, highly efficient.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema; description does not mention return values, activation, or prerequisites beyond required params. Adequate but could be more complete given tool complexity.

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 covers 100% of parameters with clear descriptions. Description adds limited additional meaning beyond stating initial creation. Baseline 3 applies; no extra value.

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?

Clearly states verb 'Create' and resource 'ABAP behavior implementation class for a behavior definition'. Specifies 'initial state', distinguishing it from UpdateBehaviorImplementation. Differentiates from sibling CreateBehaviorDefinition.

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

Usage Guidelines4/5

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

Explicitly advises using UpdateBehaviorImplementation for setting implementation code afterwards, providing clear guidance on subsequent steps. Does not address when not to use versus other create tools, but context is sufficient.

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