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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

CreateMessageClassMessage

Add a numbered message with text to an existing ABAP message class (T100) outside batch mode.

Instructions

Adds the message numbered msgno, with the text msgtext, to the existing ABAP message class (T100) named by message_class_name. 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": {
      "message_class_name": "<message_class_name>",
      "msgno": "<msgno>",
      "msgtext": "<msgtext>"
    },
    "name": "CreateMessageClassMessage"
  }
}

Input Schema

NameRequiredDescriptionDefault
msgnoYesMessage number (e.g., "001").
msgtextYesMessage text. May contain placeholders &1 &2 &3 &4 (or &).
descriptionNo(optional) Long description for the message.
self_explanatoryNo(optional) Mark the message as self-explanatory (no long text needed). Default: false.
transport_requestNo(optional) Transport request number, not a task. Required for transportable objects.
message_class_nameYesParent message class name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv16.0.0
    • changedInput schema / properties / message_class_name / description
      Previous value: -"Parent message class name (e.g., ZMY_MSGS)."New value: +"Parent message class name."
    • changedInput schema / properties / transport_request / description
      Previous value: -"(optional) Transport request number. Required for transportable objects."New value: +"(optional) Transport request number, not a task. Required for transportable objects."
  2. Addedv8.6.1

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It adds one useful trait (must run outside batch mode, relevant given the BatchBegin/BatchEnd siblings), but never states whether an existing msgno is overwritten, what permissions are required, or how transport_request interacts with the write.

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?

Two tight sentences, front-loaded with the operation and ending with the batch-mode constraint. No filler, though the parenthetical '(T100)' is a minor technical aside rather than actionable information.

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?

For a mutation tool with no annotations and no output schema, the description covers the core operation and one execution constraint. It still leaves open duplicate-handling, failure modes, and whether this is idempotent — gaps that structured fields do not fill.

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 all six parameters are documented in the schema. The description merely restates three of them (msgno, msgtext, message_class_name) without adding format, validation, or behavior detail, so the baseline 3 applies.

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?

The description names a specific verb (adds), the resource (message numbered msgno with text msgtext) and the parent object (existing ABAP message class T100). That is clearly distinct from CreateMessageClass and UpdateMessageClassMessage, though it does not name those siblings explicitly.

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?

Usage is only implied: it targets an *existing* class, so a create-class path is ruled out indirectly. The only explicit constraint is 'Runs outside batch mode', and there is no statement of when to prefer UpdateMessageClassMessage or what happens on a duplicate msgno.

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