Skip to main content
Glama

RuntimeListSystemMessages

List SM02 system messages with details on severity, validity period, and author. Filter by user, date range, or limit results.

Instructions

[runtime] List SM02 system messages. Returns structured entries with id, title, text, severity, validity period, and author.

Input Schema

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

Implementation Reference

  • Main handler function that executes the RuntimeListSystemMessages tool logic. Uses AdtRuntimeClient to fetch system messages with optional filters (user, max_results, from, to).
    export async function handleRuntimeListSystemMessages(
      context: HandlerContext,
      args: RuntimeListSystemMessagesArgs,
    ) {
      const { connection, logger } = context;
    
      try {
        const runtimeClient = new AdtRuntimeClient(connection, logger);
        const feeds = runtimeClient.getFeeds();
    
        const messages = await feeds.systemMessages({
          user: args?.user,
          maxResults: args?.max_results,
          from: args?.from,
          to: args?.to,
        });
    
        return return_response({
          data: JSON.stringify(
            {
              success: true,
              count: messages.length,
              messages,
            },
            null,
            2,
          ),
          status: 200,
          statusText: 'OK',
          headers: {},
          config: {},
        });
      } catch (error: unknown) {
        logger?.error('Error listing system messages:', error);
        return return_error(error);
      }
    }
  • Tool definition with input schema for RuntimeListSystemMessages. Defines optional parameters: user (string), max_results (number), from (string YYYYMMDDHHMMSS), to (string YYYYMMDDHHMMSS).
    export const TOOL_DEFINITION = {
      name: 'RuntimeListSystemMessages',
      available_in: ['onprem', 'cloud'] as const,
      description:
        '[runtime] List SM02 system messages. Returns structured entries with id, title, text, severity, validity period, and author.',
      inputSchema: {
        type: 'object',
        properties: {
          user: {
            type: 'string',
            description: 'Filter by author username.',
          },
          max_results: {
            type: 'number',
            description: 'Maximum number of messages to return.',
          },
          from: {
            type: 'string',
            description: 'Start of time range in YYYYMMDDHHMMSS format.',
          },
          to: {
            type: 'string',
            description: 'End of time range in YYYYMMDDHHMMSS format.',
          },
        },
        required: [],
      },
    } as const;
  • Registration of RuntimeListSystemMessages tool in SystemHandlersGroup.getHandlers() method, mapping the tool definition to the handler function.
    {
      toolDefinition: RuntimeListSystemMessages_Tool,
      handler: (args: any) =>
        handleRuntimeListSystemMessages(this.context, args),
    },
Behavior3/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It mentions that the tool 'lists' messages, implying a read-only operation, but does not explicitly state safety, rate limits, authentication needs, or side effects. The lack of such detail limits transparency to a moderate level.

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?

The description is a single, front-loaded sentence that immediately communicates the tool's purpose and output structure. Every word contributes information, with no redundancy or fluff. This is an excellent example of concise yet complete documentation.

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?

Given the absence of an output schema, the description helpfully lists the return fields (id, title, text, severity, validity period, author). It covers the essential context for a list tool with four optional parameters. Minor omissions like pagination behavior or error handling prevent a perfect score.

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 parameters are already well-documented in the schema. The description does not add any additional meaning or examples beyond what the schema provides. It merely recaps the return fields, not the parameters, so it adds no extra value for parameter usage.

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 clearly states it lists SM02 system messages, specifying the resource ('SM02') and verb ('List'). It also enumerates the returned fields, making the tool's purpose highly specific and distinct from sibling tools like 'RuntimeListFeeds' or 'RuntimeListProfilerTraceFiles'.

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?

The description includes the '[runtime]' prefix indicating a runtime operation, but does not provide explicit guidance on when to use this tool versus alternatives like 'GetTransaction' or 'RuntimeListFeeds'. It lacks when-not-to-use or prerequisite information, leaving the agent to infer context from the tool name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fr0ster/mcp-abap-adt'

If you have feedback or need assistance with the MCP directory API, please join our Discord server