Skip to main content
Glama
Hollway

mcp-abap-abap-adt-api

by Hollway
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

createMessageClass

Create a message class and populate its messages in one call, validating the name and reporting the exact step and class state if processing stops.

Instructions

Create a message class and fill in its messages in one call: validate the name, create the class, write the messages, read them back. No activation is involved. Nothing is rolled back - the answer says which step stopped and in what state the class was left. Outside $TMP a transport request is required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the new message class, e.g. ZDEV_MCP_MSG.
dryRunNoOnly validate the name and stop.
languageNoMaster language of the class. Defaults to the logon language - creating it in EN files every text where nobody will look for it.
messagesNoMessages to write straight away: [{number, text, selfExplanatory}]. Optional - an empty class is valid.
transportNoTransport request number - the request itself, not a developer task.
descriptionYesDescription of the class.
packageNameYesPackage. $TMP for a local class; anything else needs a transport request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4/5.0
Behavior4/5

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

It adds meaningful behavioral detail beyond the annotations: no activation, no rollback, partial state on failure, and transport requirements. The description explains what happens when a step fails, which is critical for an agent to reason about consequences.

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?

Three dense, purposeful sentences with no filler. The action is front-loaded, and every sentence adds operational or behavioral value.

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?

For a 7-parameter, no-output-schema tool, it explains the key behavioral risks, the execution sequence, and the transport constraint. It could be slightly more explicit about required-parameter relationships, but the schema fills most gaps.

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 the baseline is 3. The description adds a little semantic glue, such as 'validate the name' and 'write the messages', but most parameter meaning is already supplied in the schema.

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?

The description uses a specific verb and resource: 'create a message class and fill in its messages in one call'. It clearly distinguishes this from single-step create or message-writing tools by emphasizing the combined workflow and the 'no activation' behavior.

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?

It gives practical context such as transport requirements and the non-transactional execution, which helps an agent decide where this tool fits. However, it does not explicitly state when to prefer this over related siblings like setMessages or createObject.

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