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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

RuntimeListSystemMessages

Lists SM02 system messages with optional time range, author, and result-limit filters, returning structured entries with severity, validity period, and author for runtime monitoring.

Instructions

[read-only] [runtime] List SM02 system messages. Returns structured entries with id, title, text, severity, validity period, and author. 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "RuntimeListSystemMessages"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd of time range in YYYYMMDDHHMMSS format.
fromNoStart of time range in YYYYMMDDHHMMSS format.
userNoFilter by author username.
max_resultsNoMaximum number of messages to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv6.5.1

TDQS

A3.5/5.0
Behavior4/5

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

With annotations absent, the description carries the full burden and does reasonably well: it declares read-only, enumerates the return fields, and explains the non-obvious batch-mode recording semantics (recorded under next number, empty content, read back by number). It omits permission requirements and pagination/truncation behavior, which keeps it short of 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-loaded with the [read-only]/[runtime] tags and core purpose, and every sentence carries information. The batch-mode sentence is dense but relevant, not filler.

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, so the description's field enumeration is valuable, and the lack of annotations is offset by the explicit read-only declaration and batch behavior note. Remaining gaps (pagination handling, empty-result behavior) are minor for a filtered list tool.

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 four parameters (from, to, user, max_results) are already documented with formats in the schema. The description adds no syntax or semantics beyond mentioning 'validity period', so the baseline of 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?

States a specific verb 'List' and resource 'SM02 system messages', plus enumerates the returned fields (id, title, text, severity, validity period, author). It doesn't explicitly differentiate from sibling runtime tools, but no sibling appears to overlap on SM02 messages, so an agent can still identify the target resource.

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

Usage Guidelines2/5

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

Provides no when-to-use, when-not-to-use, or alternative-tool guidance. The batch-mode sentence describes behavior after invocation, not a condition that selects this tool, so an agent gets no routing signal from usage guidance itself.

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