Skip to main content
Glama
ethanhan2014

SAP ADT MCP Server

by ethanhan2014

get_function_module

Retrieve the source code of an SAP function module by specifying its function group and name. Optionally target a specific SAP system ID.

Instructions

Fetch function module source code from SAP system

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
function_groupYesFunction group name (e.g. 2032)
function_nameYesFunction module name (e.g. SD_SALESDOCUMENT_CREATE)
system_idNoSAP system ID (e.g. DEV). Omit to use default system.

Implementation Reference

  • Registration of the get_function_module tool in the MCP tool list with its name, description, and input schema.
    {
      name: "get_function_module",
      description: "Fetch function module source code from SAP system",
      inputSchema: {
        type: "object" as const,
        properties: {
          function_group: { type: "string", description: "Function group name (e.g. 2032)" },
          function_name: { type: "string", description: "Function module name (e.g. SD_SALESDOCUMENT_CREATE)" },
          ...SYSTEM_ID_PROP,
        },
        required: ["function_group", "function_name"],
      },
    },
  • Zod schema for validating the function_group and function_name input parameters for get_function_module.
    const FunctionModuleSchema = z.object({
      function_group: z.string(),
      function_name: z.string(),
    });
  • Handler logic for get_function_module: parses the function_group and function_name, constructs the SAP ADT REST URL for function module source, and returns the source code.
    case "get_function_module": {
      const { function_group, function_name } = FunctionModuleSchema.parse(args);
      const source = await client.getSource(
        `/sap/bc/adt/functions/groups/${encodeURIComponent(function_group.toUpperCase())}/fmodules/${encodeURIComponent(function_name.toUpperCase())}/source/main`
      );
      return { content: [{ type: "text", text: source }] };
    }
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states a fetch operation without confirming read-only nature, potential side effects, or permissions required.

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 with no extraneous words. It efficiently conveys the core purpose.

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 has 3 parameters, no output schema, and no annotations, the description is minimally adequate but does not explain return format, error handling, or integration with SAP system states.

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 has 100% coverage, meaning all three parameters have descriptions. The added description 'Fetch function module source code' does not provide additional semantic detail beyond the schema.

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 'Fetch function module source code from SAP system' uses a specific verb ('fetch') and clearly identifies the resource ('function module source code'). It distinguishes from sibling tools like 'get_function_group' and 'get_class' by specifying 'function module'.

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 is provided on when to use this tool versus alternatives such as 'get_function_group' or 'get_class'. There is no mention of prerequisites, preferred contexts, or exclusions.

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