Skip to main content
Glama
NicoHern

ABAPilot

by NicoHern
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
JavaScript
Remote

sap_read_jobs

Retrieve SAP background job details from SM37, including status, execution times, and scheduling information. Filter by user, status, date range, or job name prefix to monitor job outcomes.

Instructions

Query background job information from SAP's SM37 transaction. Returns job status, execution times, and scheduling details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userNoFilter by scheduling user
statusNoJob status: F=Finished, A=Aborted, R=Running, S=Scheduled, P=Ready
date_toNoEnd date in YYYYMMDD format (default: today)
job_nameNoFilter by job name prefix
max_rowsNoMaximum rows to return
date_fromNoStart date in YYYYMMDD format (default: last 7 days)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed15 schema fields changedv0.1.2
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / date_from / description
      Previous value: -"Start date YYYYMMDD (default last 7 days)"New value: +"Start date in YYYYMMDD format (default: last 7 days)"
    • addedInput schema / properties / date_from / example
      Added value: +"20260101"
    • changedInput schema / properties / date_to / description
      Previous value: -"End date YYYYMMDD"New value: +"End date in YYYYMMDD format (default: today)"
    • addedInput schema / properties / date_to / example
      Added value: +"20260131"
    • changedInput schema / properties / job_name / description
      Previous value: -"Job name prefix filter"New value: +"Filter by job name prefix"
    • addedInput schema / properties / job_name / example
      Added value: +"ZPROG_"
    • addedInput schema / properties / max_rows / default
      Added value: +100
    • changedInput schema / properties / max_rows / description
      Previous value: -"Maximum rows (default 100)"New value: +"Maximum rows to return"
    • addedInput schema / properties / max_rows / example
      Added value: +100
    • changedInput schema / properties / max_rows / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / status / description
      Previous value: -"F, A, R, S or P"New value: +"Job status: F=Finished, A=Aborted, R=Running, S=Scheduled, P=Ready"
    • addedInput schema / properties / status / enum
      Added value: +[
+  "F",
+  "A",
+  "R",
+  "S",
+  "P"
+]
    • addedInput schema / properties / user / example
      Added value: +"BATCH"
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. 'Query' and 'Returns' clearly signal a read-only operation and indicate that no mutation is involved. It does not mention authorization or rate limits, but these are less critical for a query tool with obvious read semantics.

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 two tight sentences with no wasted words. The action and source are front-loaded, followed by a concise statement of what the tool returns.

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 an optional-parameter read tool with a fully documented schema, the description provides sufficient context about the tool's purpose and output. It does not go deep into edge-case behavior or explicitly compare against sibling tools, but nothing critical is missing for selecting and invoking the 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?

The input schema already provides 100% coverage, including descriptions, examples, defaults, and an enum for status. The description adds high-level context about returned job information but does not need to restate parameter details because the schema fully documents them.

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 identifies the operation as querying background job information from SAP's SM37 transaction. It names the specific resource and the types of data returned, so an agent can distinguish it from general table-read and diagnostic 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?

The description makes the context obvious: use this tool when background job information is needed, such as job status, execution times, or scheduling details. It does not explicitly name alternatives or exclusions, but the purpose is specific enough to guide selection among the many sibling SAP tools.

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/NicoHern/abapilot-mcp'

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