Skip to main content
Glama
AnindyaDR-SAP

mcp-abap-adt

by AnindyaDR-SAP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetTransaction

Retrieve ABAP transaction details, with optional line-based paging for large outputs.

Instructions

Retrieve ABAP transaction details. For large results, use startLine/maxLines to page through it instead of retrieving it all at once.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxLinesNoMaximum lines to return (1-100000). Omit to request the rest; the byte cap may return fewer lines.
startLineNo1-based line number to start from (default 1). Beyond EOF returns an empty page with hasMore=false.
transaction_nameYesName of the ABAP transaction

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It mentions pagination behavior and that the byte cap may return fewer lines, which is useful. However, it does not disclose the return format or whether the operation is read-only, but that is implied by 'retrieve' and the sibling set.

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?

The description is short and to the point, with the pagination advice front-loaded. It is not verbose and every sentence adds value. It could be improved by separating the pagination hint from the main purpose, but it's still concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (3 params, all documented, no output schema), the description is adequate. It covers the main retrieval and pagination. It doesn't specify the exact structure of the response, but without an output schema, an agent might wonder what fields are returned, which is a minor gap.

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 well-documented in the schema. The description adds a bit by explaining the purpose of startLine/maxLines for pagination, but it doesn't add much beyond that. Baseline 3 is appropriate.

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?

The description clearly states the tool retrieves ABAP transaction details, with a specific verb and resource. It is distinguishable from sibling tools like GetProgram or GetTable, though it could more explicitly say it returns source code or metadata, but the name and description are sufficiently clear.

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 provides guidance on when to use pagination (for large results) and how to page through with startLine/maxLines. It doesn't explicitly mention when not to use this tool versus siblings, but the context is clear enough for an agent to infer it's the right tool for transactions.

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