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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetMessageClassMessage

Fetches one ABAP message by class name and message number, returning its text, self-explanatory and long-text flags, last changer, and change time.

Instructions

[read-only] Reads the message numbered msgno of the ABAP message class (MSAG/T100) named by message_class_name in one request. Answers the one message under message: its number (msgno), text (msgtext), self-explanatory flag (selfexplainatory), long-text flag (documented), last changer (lastchangedby), change time (lastmodified), and every other field the system gives the message. A number absent from the class is refused as missing. 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": {
      "message_class_name": "<message_class_name>",
      "msgno": "<msgno>"
    },
    "name": "GetMessageClassMessage"
  }
}

Input Schema

NameRequiredDescriptionDefault
msgnoYesMessage number (e.g., "001").
detailNoHow much of the answer to return: "terse" (default, the fields you need to act), "full" (the whole parse), "raw" (the document as ADT sent it).terse
message_class_nameYesParent message class name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv20.1.0
    • addedInput schema / properties / detail
      Added value: +{
+  "default": "terse",
+  "description": "How much of the answer to return: \"terse\" (default, the fields you need to act), \"full\" (the whole parse), \"raw\" (the document as ADT sent it).",
+  "enum": [
+    "terse",
+    "full",
+    "raw"
+  ],
+  "type": "string"
+}
  2. Changed1 schema field 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."
  3. Addedv8.6.1

TDQS

A4.3/5.0
Behavior5/5

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

No annotations are supplied, so the description carries the full burden and does so well: it self-declares read-only, enumerates the returned fields, specifies the missing-number error, and explains batch-mode recording semantics (call recorded under the next number, empty content, answer read by number afterward). That batch caveat is exactly the kind of non-obvious behavior an agent cannot infer from the schema.

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-loaded with the read-only marker and the verb+resource, then the return shape, then edge cases. Padding exists ('and every other field the system gives the message'), and the batch sentence is dense, but every sentence contributes usable 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?

With no output schema, the description compensates by enumerating the key returned fields plus error and batch behavior. The one gap is the unmentioned detail parameter, which means the described 'every other field' answer does not visibly reconcile with the default terse projection.

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 the baseline is 3. The description reinforces msgno as a number within the class and message_class_name as the MSAG/T100 class name, but it never mentions the detail parameter (terse/full/raw), which materially changes the returned payload.

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?

States a specific verb and resource: reads the one message numbered msgno from the ABAP message class (MSAG/T100) named by message_class_name. The singular 'one message' scope cleanly separates it from the sibling GetMessageClass and the Create/Update/DeleteMessageClassMessage tools.

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?

Establishes a clear when-to-use context (fetch exactly one message by class plus number) and adds an explicit failure condition: a number absent from the class is refused as missing. It does not explicitly route the agent to GetMessageClass for listing a whole class, so the alternative-handling is implied rather than stated.

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