Skip to main content
Glama
ethanhan2014

SAP ADT MCP Server

by ethanhan2014

get_transaction

Fetch ABAP transaction details (package, application component) from SAP systems by providing a transaction code. Optionally specify the system ID to target a specific SAP system.

Instructions

Fetch ABAP transaction details (package, application component) from SAP system

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesTransaction code (e.g. VA01)
system_idNoSAP system ID (e.g. DEV). Omit to use default system.

Implementation Reference

  • Tool registration for 'get_transaction' in the ListToolsRequestSchema handler - defines the tool name, description, and input schema.
    {
      name: "get_transaction",
      description: "Fetch ABAP transaction details (package, application component) from SAP system",
      inputSchema: {
        type: "object" as const,
        properties: { name: { type: "string", description: "Transaction code (e.g. VA01)" }, ...SYSTEM_ID_PROP },
        required: ["name"],
      },
    },
  • Handler implementation for 'get_transaction' tool - parses the name argument and calls client.getTransactionDetails().
    case "get_transaction": {
      const { name: txName } = NameSchema.parse(args);
      const details = await client.getTransactionDetails(txName);
      return { content: [{ type: "text", text: details }] };
    }
  • Helper method AdtClient.getTransactionDetails() - makes an HTTP GET request to the SAP ADT object properties API to fetch transaction details (package, application component).
    async getTransactionDetails(name: string): Promise<string> {
      const adtUri = `/sap/bc/adt/vit/wb/object_type/trant/object_name/${encodeURIComponent(name.toUpperCase())}`;
      const response = await this.http.get<string>(
        `/sap/bc/adt/repository/informationsystem/objectproperties/values?uri=${encodeURIComponent(adtUri)}&facet=package&facet=appl`,
        { headers: { Accept: "*/*" }, responseType: "text" }
      );
      return response.data;
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does not mention behavioral traits such as required permissions, potential errors, or any side effects. The read-only nature is implied but not stated, and there is no discussion of limitations or safety considerations.

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 sentence that efficiently conveys the core purpose. No unnecessary words or redundancy. It is well-structured and front-loaded with the primary action.

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 a simple tool with two parameters and no output schema, the description covers the essential purpose and what is fetched. However, it could be slightly improved by specifying the return format (e.g., an object with package and application component). Overall, it is adequate but not fully comprehensive.

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 schema already documents both parameters. The description adds minimal extra meaning beyond the schema (e.g., examples for transaction code and system ID). It meets the baseline but does not provide deeper insight into parameter relationships or constraints.

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 uses a specific verb 'Fetch' and clearly identifies the resource 'ABAP transaction details (package, application component)'. It distinguishes itself from sibling tools like 'get_transport' or 'get_package' by focusing on transaction details.

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 implies usage when you need transaction details, but it does not explicitly state when to use this tool versus alternatives, nor does it provide exclusions or prerequisites. The context of sibling tools provides implicit differentiation.

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/ethanhan2014/sap-adt-mcp'

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