Skip to main content
Glama
ethanhan2014

SAP ADT MCP Server

by ethanhan2014

get_include

Fetch ABAP include source code from SAP systems. Provide the include name and optionally the system ID to retrieve the source code directly.

Instructions

Fetch ABAP include source code from SAP system

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesInclude name (e.g. LSVATF01)
system_idNoSAP system ID (e.g. DEV). Omit to use default system.

Implementation Reference

  • The 'get_include' tool is registered in the ListToolsRequestSchema handler with its name, description, and input schema (requires a 'name' string property and optional system_id).
      name: "get_include",
      description: "Fetch ABAP include source code from SAP system",
      inputSchema: {
        type: "object" as const,
        properties: { name: { type: "string", description: "Include name (e.g. LSVATF01)" }, ...SYSTEM_ID_PROP },
        required: ["name"],
      },
    },
  • Input schema for get_include: expects { name: string } as required, with optional system_id property from SYSTEM_ID_PROP.
    inputSchema: {
      type: "object" as const,
      properties: { name: { type: "string", description: "Include name (e.g. LSVATF01)" }, ...SYSTEM_ID_PROP },
      required: ["name"],
    },
  • The handler for 'get_include' tool: parses args with NameSchema, calls client.getSource() with the URI path /sap/bc/adt/programs/includes/{name}/source/main to fetch the ABAP include source code.
    case "get_include": {
      const { name: inclName } = NameSchema.parse(args);
      const source = await client.getSource(
        `/sap/bc/adt/programs/includes/${encodeURIComponent(inclName.toUpperCase())}/source/main`
      );
      return { content: [{ type: "text", text: source }] };
    }
Behavior2/5

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

With no annotations, the description should disclose behavioral traits. It only states the action without mentioning permissions, side effects, or output nature. Minimal transparency.

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 a single concise sentence with no wasted words. However, it could be slightly more informative without loss of conciseness.

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 simple tool with two parameters, the description is somewhat complete but lacks context on output format, prerequisites, or default behavior. Not fully sufficient for an agent to use confidently.

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 explains parameters. The description adds no additional meaning beyond what the schema provides, resulting in a baseline score of 3.

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 'Fetch ABAP include source code from SAP system', using a specific verb and resource. It distinguishes from sibling tools like get_abap_program or get_class by specifying the ABAP include type.

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?

No guidance on when to use this tool versus alternatives (e.g., get_abap_program for programs, get_class for classes). The description lacks context for selection.

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