Skip to main content
Glama

sap-system-update

Destructive

Create or update SAP system configurations for RFC connector targets in Simplifier projects, including system parameters, project assignments, and connection settings.

Instructions

#Create or update a SAP system

SAP Systems are used as the target of RFC connectors.

Attention: When updating tags, allways fetch the SAP system resource first to ensure operating on the latest version. Existing tags have to be resent when doing an update - otherwise they would be cleared.

You can find existing SAP systems with the simplifier://sap-systems resource, and details about a single system with simplifier://sap-system/{systemName}

Project Assignment

SAP systems must be assigned to projects using the project assignment parameters:

For Creating New SAP Systems:

  • Set projectsBefore to empty array []

  • Set projectsAfterChange to array of project names to assign the SAP system to

For Updating Existing SAP Systems:

  • Set projectsBefore to current project assignments (from existing SAP system)

  • Set projectsAfterChange to new project assignments

Example:

{
  "name": "MySapSystem",
  "projectsBefore": [],
  "projectsAfterChange": ["ProjectA", "ProjectB"]
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
descriptionYes
activeNoenables or disables the SAP system. Should be true, if you want to use the system
instanceRestrictionsYesrestrict this system to specific Simplifier instances, it isn't transported to unlisted instances. If this is empty, no restriction is applied
systemTypeNoThe type of your SAP System (e.g. Development, Testing, Production…)
configurationYes
tagsYesArray of tags for categorizing and organizing this SAP system. If not provided when updating, existing tags will be preserved.
projectsBeforeNoProject names before the change. Use empty array [] when creating new SAP systems, or provide current projects when updating.
projectsAfterChangeNoProject names to assign the SAP system to. Required for tracking project assignments.

Implementation Reference

  • The asynchronous handler function that implements the core logic of the 'sap-system-update' tool. It checks if the SAP system exists, constructs the SAPSystem data object, and calls either createSapSystem or updateSapSystem on the SimplifierClient.
    }, async ({ name, description, active, instanceRestrictions, systemType, configuration, tags, projectsBefore, projectsAfterChange }) => {
      return wrapToolResult(`create or update SAP system ${name}`, async () => {
        const trackingKey = trackingToolPrefix + toolNameSapSystemUpdate;
        let oExisting: any;
        try { oExisting = await simplifier.getSapSystem(name, trackingKey) } catch { }
    
        const data: SAPSystem = {
          name: name,
          description: description,
          active: active,
          instanceRestrictions: instanceRestrictions,
          systemType: systemType || "",
          configuration: {
            ...configuration,
            sapRouterString: configuration.sapRouterString || "",
            sncQualityOfProtection: sncProtectionQualities[configuration.sncQualityOfProtection] || 3,
          },
          tags: tags,
          assignedProjects: {
            projectsBefore: projectsBefore || [],
            projectsAfterChange: projectsAfterChange || []
          },
          permission: {
            deletable: true,
            editable: true,
          },
        }
        if (oExisting) {
          return simplifier.updateSapSystem(data);
        } else {
          return simplifier.createSapSystem(data)
        }
      })
  • Zod schema defining the input parameters and validation for the 'sap-system-update' tool, including SAP system details, configuration, tags, and project assignments.
      name: z.string(),
      description: z.string(),
      active: z.boolean().describe('enables or disables the SAP system. Should be true, if you want to use the system').default(true),
      instanceRestrictions: z.array(z.string()).describe("restrict this system to specific Simplifier instances, it isn't transported to unlisted instances. If this is empty, no restriction is applied"),
      systemType: z.string().describe("The type of your SAP System (e.g. Development, Testing, Production…)").optional(),
      configuration: z.object({
        systemId: z.string().describe("SAP system id"),
        systemNumber: z.string().describe("SAP system number (00-99)"),
        clientNumber: z.string().describe("SAP client number (000-999) "),
        language: z.string().describe("The language in which the SAP system should return translatable values"),
        applicationServerHostname: z.string().describe("hostname or ip of the application server"),
        sapRouterString: z.string().describe("The string used to connect via SAP-Router to your SAP System").optional(),
        sncActive: z.boolean().describe("Enable SNC for the connection"),
        sncPartner: z.string().describe("the SNC communication partner (e.g. your SAP system)"),
        sncSsoMode: z.boolean().describe("With this switch you can select to use SNC-SSO (SNC Single Sign On) Mode"),
        sncQualityOfProtection: z.enum([
          "authentication", "integrity+authentication", "privacy+integrity+authentication", "default", "maximum",
        ]).describe("sets the SNC quality of protection level").optional().default("privacy+integrity+authentication"),
      }),
      tags: z.array(z.string()).describe('Array of tags for categorizing and organizing this SAP system. If not provided when updating, existing tags will be preserved.'),
      projectsBefore: z.array(z.string()).default([]).describe('Project names before the change. Use empty array [] when creating new SAP systems, or provide current projects when updating.'),
      projectsAfterChange: z.array(z.string()).default([]).describe('Project names to assign the SAP system to. Required for tracking project assignments.')
    },
  • The MCP server.tool registration call that defines and registers the 'sap-system-update' tool, including its name, description, input schema, hints, and handler function.
    server.tool(toolNameSapSystemUpdate,
      sapSystemUpdateDescription,
      {
        name: z.string(),
        description: z.string(),
        active: z.boolean().describe('enables or disables the SAP system. Should be true, if you want to use the system').default(true),
        instanceRestrictions: z.array(z.string()).describe("restrict this system to specific Simplifier instances, it isn't transported to unlisted instances. If this is empty, no restriction is applied"),
        systemType: z.string().describe("The type of your SAP System (e.g. Development, Testing, Production…)").optional(),
        configuration: z.object({
          systemId: z.string().describe("SAP system id"),
          systemNumber: z.string().describe("SAP system number (00-99)"),
          clientNumber: z.string().describe("SAP client number (000-999) "),
          language: z.string().describe("The language in which the SAP system should return translatable values"),
          applicationServerHostname: z.string().describe("hostname or ip of the application server"),
          sapRouterString: z.string().describe("The string used to connect via SAP-Router to your SAP System").optional(),
          sncActive: z.boolean().describe("Enable SNC for the connection"),
          sncPartner: z.string().describe("the SNC communication partner (e.g. your SAP system)"),
          sncSsoMode: z.boolean().describe("With this switch you can select to use SNC-SSO (SNC Single Sign On) Mode"),
          sncQualityOfProtection: z.enum([
            "authentication", "integrity+authentication", "privacy+integrity+authentication", "default", "maximum",
          ]).describe("sets the SNC quality of protection level").optional().default("privacy+integrity+authentication"),
        }),
        tags: z.array(z.string()).describe('Array of tags for categorizing and organizing this SAP system. If not provided when updating, existing tags will be preserved.'),
        projectsBefore: z.array(z.string()).default([]).describe('Project names before the change. Use empty array [] when creating new SAP systems, or provide current projects when updating.'),
        projectsAfterChange: z.array(z.string()).default([]).describe('Project names to assign the SAP system to. Required for tracking project assignments.')
      },
      {
        title: "Create or update a SAP system",
        readOnlyHint: false,
        destructiveHint: true,
        idempotentHint: false,
        openWorldHint: true
      }, async ({ name, description, active, instanceRestrictions, systemType, configuration, tags, projectsBefore, projectsAfterChange }) => {
        return wrapToolResult(`create or update SAP system ${name}`, async () => {
          const trackingKey = trackingToolPrefix + toolNameSapSystemUpdate;
          let oExisting: any;
          try { oExisting = await simplifier.getSapSystem(name, trackingKey) } catch { }
    
          const data: SAPSystem = {
            name: name,
            description: description,
            active: active,
            instanceRestrictions: instanceRestrictions,
            systemType: systemType || "",
            configuration: {
              ...configuration,
              sapRouterString: configuration.sapRouterString || "",
              sncQualityOfProtection: sncProtectionQualities[configuration.sncQualityOfProtection] || 3,
            },
            tags: tags,
            assignedProjects: {
              projectsBefore: projectsBefore || [],
              projectsAfterChange: projectsAfterChange || []
            },
            permission: {
              deletable: true,
              editable: true,
            },
          }
          if (oExisting) {
            return simplifier.updateSapSystem(data);
          } else {
            return simplifier.createSapSystem(data)
          }
        })
      });
Behavior4/5

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

The description adds valuable behavioral context beyond annotations: it warns about tag clearing during updates (requiring fetching the latest version first) and explains project assignment logic. Annotations already indicate this is a destructive, non-idempotent write operation (destructiveHint: true, idempotentHint: false), but the description provides specific implementation details that help the agent use the tool correctly.

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 well-structured with clear sections (purpose, attention warning, resource references, project assignment rules, example). While somewhat lengthy, every section serves a purpose: the warning about tags is crucial, the project assignment explanation is necessary for correct usage, and the example clarifies complex parameter interactions.

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 complex tool with 9 parameters, nested objects, no output schema, and destructive annotations, the description provides substantial context: it explains the tool's role in the ecosystem, gives implementation warnings, details project assignment logic, and provides usage examples. The main gap is lack of information about return values or error handling, but overall it's quite comprehensive.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 67% schema description coverage, the description compensates well by explaining critical parameter semantics: it details the purpose and usage of 'projectsBefore' and 'projectsAfterChange' parameters with clear examples, and provides important warnings about 'tags' parameter behavior during updates. This adds significant value beyond the schema's technical descriptions.

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 the tool's purpose as 'Create or update a SAP system' and explains that SAP Systems are used as targets for RFC connectors. It distinguishes from siblings like 'sap-system-delete' by focusing on creation/update operations rather than deletion.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use this tool versus alternatives: it references finding existing systems with 'simplifier://sap-systems' and details with 'simplifier://sap-system/{systemName}'. It also gives clear instructions for creating vs. updating scenarios, including project assignment rules and tag handling warnings.

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/simplifier-ag/simplifier-mcp'

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