Skip to main content
Glama

connector-update

Create or update connectors for REST, SOAP, and SAP RFC integrations in the Simplifier platform. Configure endpoints, SSL settings, and project assignments to establish or modify system connections.

Instructions

Create or update a Connector

This tool allows to

  • create new connectors

  • modify existing connectors

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

Connector Types

Common settings

For all connectors using SSL / TLS, the sslSettings option has two fields:

  • trustType: An integer, with the following meaning:

    • 0: Always trust any certificate, regardless of CA signing

    • 1: Only trust the certificate specified explicitly

    • 2: Use system certificates for trust

    • 3: Combination of 1+2, trust explicitly specified certificate and any system trusted certificate.

  • ignoreSSLCertificates: boolean, if set to true, any TLS validation will be skipped and the target will always be trusted, even when the certificate does not match the hostname.

When no SSL is required, or no specific settings apply, use the following sslSettings:

{
"trustType": 2,
"ignoreSSLCertificates": false
}

Connector type 'REST'

The object under endpointConfiguration / configuration defines properties, specific to REST Connector:

  • endpointURL - the actual address of the remote REST endpoint

  • sslSettings - SSL related options.

Complete Example:

{
  "name": "TestCreate",
  "description": "",
  "connectorType": "REST",
  "active": true,
  "timeoutTime": 60,
  "endpointConfiguration": {
    "endpoint": "Default",
    "certificates": [],
    "configuration": {
      "endpointURL": "http://example-api.com/bla",
      "sslSettings": {
        "trustType": 2,
        "ignoreSSLCertificates": false
      }
    }
  },
  "tags": [],
  "assignedProjects": {
    "projectsAfterChange": []
  }
}

Connector type 'SOAP'

The object under endpointConfiguration / configuration defines properties, specific to SOAP Connector:

  • wsdlUrl - the address of a WSDL specification, which is used for the connector

  • sslSettings - SSL related options.

Complete Example:

{
  "name": "TestCreate",
  "description": "",
  "connectorType": "SOAP",
  "active": true,
  "timeoutTime": 60,
  "endpointConfiguration": {
    "endpoint": "Default",
    "certificates": [],
    "configuration": {
      "wsdlUrl": "http://example-soap.com/myService?wsdl",
      "sslSettings": {
        "trustType": 2,
        "ignoreSSLCertificates": false
      }
    }
  },
  "tags": [],
  "assignedProjects": {
    "projectsAfterChange": []
  }
}

Connector type 'SAP RFC'

The object under endpointConfiguration / configuration defines the following properties specific to SAP RFC connectors, all of them are mandatory:

  • sapSystem - ID of the target SAP system as a string.

  • parallelExecutions - Boolean. If true, batch calls (i.e. multiple function modules are executed in one call) are executed in parallel.

  • connectionPool - object with settings related to connection pooling:

    • peakLimit - number, maximum number of active connections at a time.

    • poolCapacity - number of pooled connections.

    • expirationTime - time in milliseconds for which connections are kept in the pool before being closed.

    • expirationCheckPeriod - time in milliseconds between checks for expired pooled connections.

    • maxGetClientTime - maximum time in milliseconds to wait for getting a connection (i.e. connection timeout).

Complete example:

{
  "name": "MyRfc",
  "description": "",
  "connectorType": "SAPRFC",
  "active": true,
  "timeoutTime": 60,
  "endpointConfiguration": {
    "endpoint": "Default",
    "certificates": [],
    "configuration": {
      "sapSystem": "ID4_0_800",
      "parallelExecutions": false,
      "connectionPool": {
        "peakLimit": 0,
        "poolCapacity": 1,
        "expirationTime": 60000,
        "expirationCheckPeriod": 60000,
        "maxGetClientTime": 30000
      }
    }
  },
  "tags": [],
  "assignedProjects": {
    "projectsAfterChange": []
  }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
descriptionNo
connectorTypeYes
activeNo
timeoutTimeNomaximum duration of a call in seconds
endpointConfigurationNoOn creating a new connector, an endpoint configuration is mandatory. On updating a Connector: * endpoint configuration may be omitted if it is not intended to change. * a new endpoint configuration can be added by using a new endpoint name. * one endpoint configuration can be changed by using the name property of an existing configuration.
tagsNo
projectsBeforeNoProject names before the change. Use empty array [] when creating new Connectors, or provide current projects when updating.
projectsAfterChangeNoProject names to assign the Connector to. Required for tracking project assignments.

Implementation Reference

  • The handler function that implements the core logic of the 'connector-update' tool. It determines if the connector exists, constructs the data payload, and invokes either createConnector or updateConnector on the SimplifierClient.
    async ( {name, description, connectorType, active, timeoutTime, endpointConfiguration, tags, projectsBefore, projectsAfterChange}) => {
      return wrapToolResult( `create or update Connector ${name}`, async () => {
        const trackingKey = trackingToolPrefix + toolNameConnectorUpdate
        let oExisting: any;
        try { oExisting = await simplifier.getConnector(name, trackingKey) } catch {}
        const oConnectorData = {
          name: name,
          description: description,
          connectorType: connectorType,
          active: active,
          timeoutTime: timeoutTime,
          endpointConfiguration: endpointConfiguration,
          tags: tags,
          assignedProjects: {
            projectsBefore: projectsBefore,
            projectsAfterChange: projectsAfterChange
          }
        } as SimplifierConnectorUpdate
    
        if (oExisting?.name) {
          return simplifier.updateConnector(oConnectorData);
        } else {
          if (!oConnectorData.endpointConfiguration) {
            throw new Error('endpointConfiguration is required on creating a new connector!');
          }
          return simplifier.createConnector(oConnectorData)
        }
      })
    });
  • Zod schema defining the input parameters and validation for the 'connector-update' tool, including connector details, endpoint configuration, tags, and project assignments.
          inputSchema: {
            name: z.string(),
            description: z.string().optional().default(""),
            connectorType: z.string(),
            active: z.boolean().optional().default(true),
            timeoutTime: z.number().optional().default(60)
              .describe(`maximum duration of a call in seconds`),
            endpointConfiguration: z.object({
              endpoint: z.string()
                .describe(`The name of an existing instance, defined at the Simplifier server landscape.
    **Use the name of the active instance, provided by simplifier://server-active-instance when creating 
    a connector endpoint for the server, you are currently working on.**
    HINT: In error messages, endpoint names are often eclosed in brackets [] or quotes for readability. 
    **When using endpoint name from error message, strip off brackets and quotes**
              `),
              certificates: z.array(z.string()),
              configuration: z.any().optional()
                .describe(`The properties, defined by this object are specific to the chosen connectorType`),
              loginMethodName: z.string().optional()
                .describe(`The name of an existing login method, available on the Simplifier server`),
            }).optional()
              .describe(
                `On creating a new connector, an endpoint configuration is mandatory. 
    On updating a Connector:
    * endpoint configuration may be omitted if it is not intended to change. 
    * a new endpoint configuration can be added by using a new endpoint name. 
    * one endpoint configuration can be changed by using the name property of an existing configuration. 
            `),
            tags: z.array(z.string()).optional().default([]),
            projectsBefore: z.array(z.string()).optional().default([])
              .describe('Project names before the change. Use empty array [] when creating new Connectors, or provide current projects when updating.'),
            projectsAfterChange: z.array(z.string()).optional().default([])
              .describe('Project names to assign the Connector to. Required for tracking project assignments.')
          },
  • The server.registerTool call that registers the 'connector-update' tool with its description, input schema, annotations, and handler function.
      server.registerTool(toolNameConnectorUpdate,
        {
          description: toolDescriptionConnectorUpdate,
          inputSchema: {
            name: z.string(),
            description: z.string().optional().default(""),
            connectorType: z.string(),
            active: z.boolean().optional().default(true),
            timeoutTime: z.number().optional().default(60)
              .describe(`maximum duration of a call in seconds`),
            endpointConfiguration: z.object({
              endpoint: z.string()
                .describe(`The name of an existing instance, defined at the Simplifier server landscape.
    **Use the name of the active instance, provided by simplifier://server-active-instance when creating 
    a connector endpoint for the server, you are currently working on.**
    HINT: In error messages, endpoint names are often eclosed in brackets [] or quotes for readability. 
    **When using endpoint name from error message, strip off brackets and quotes**
              `),
              certificates: z.array(z.string()),
              configuration: z.any().optional()
                .describe(`The properties, defined by this object are specific to the chosen connectorType`),
              loginMethodName: z.string().optional()
                .describe(`The name of an existing login method, available on the Simplifier server`),
            }).optional()
              .describe(
                `On creating a new connector, an endpoint configuration is mandatory. 
    On updating a Connector:
    * endpoint configuration may be omitted if it is not intended to change. 
    * a new endpoint configuration can be added by using a new endpoint name. 
    * one endpoint configuration can be changed by using the name property of an existing configuration. 
            `),
            tags: z.array(z.string()).optional().default([]),
            projectsBefore: z.array(z.string()).optional().default([])
              .describe('Project names before the change. Use empty array [] when creating new Connectors, or provide current projects when updating.'),
            projectsAfterChange: z.array(z.string()).optional().default([])
              .describe('Project names to assign the Connector to. Required for tracking project assignments.')
          },
          annotations: {
            title: "Create or update a Connector",
            readOnlyHint: false,
            destructiveHint: false,
            idempotentHint: false,
            openWorldHint: true
          },
        },
        async ( {name, description, connectorType, active, timeoutTime, endpointConfiguration, tags, projectsBefore, projectsAfterChange}) => {
          return wrapToolResult( `create or update Connector ${name}`, async () => {
            const trackingKey = trackingToolPrefix + toolNameConnectorUpdate
            let oExisting: any;
            try { oExisting = await simplifier.getConnector(name, trackingKey) } catch {}
            const oConnectorData = {
              name: name,
              description: description,
              connectorType: connectorType,
              active: active,
              timeoutTime: timeoutTime,
              endpointConfiguration: endpointConfiguration,
              tags: tags,
              assignedProjects: {
                projectsBefore: projectsBefore,
                projectsAfterChange: projectsAfterChange
              }
            } as SimplifierConnectorUpdate
    
            if (oExisting?.name) {
              return simplifier.updateConnector(oConnectorData);
            } else {
              if (!oConnectorData.endpointConfiguration) {
                throw new Error('endpointConfiguration is required on creating a new connector!');
              }
              return simplifier.createConnector(oConnectorData)
            }
          })
        });
  • Top-level registration call in tools index that invokes connectorTools registration, which includes the 'connector-update' tool.
    registerConnectorTools(server, simplifier)
  • TypeScript interface defining the structure for connector update/create payload used in the handler.
    export interface SimplifierConnectorUpdate {
      name: string;
      description: string;
      connectorType: string;
      endpointConfiguration?: DetailedEndpoint | undefined;
      active: boolean;
      timeoutTime: number;
      tags: string[];
      assignedProjects: {
        projectsBefore: string[];
        projectsAfterChange: string[];
      };
    }
Behavior4/5

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

The description adds valuable behavioral context beyond what annotations provide. While annotations indicate this is a write operation (readOnlyHint: false) and not destructive, the description warns about data loss during updates ('Existing tags and endpoints have to be resent when doing an update - otherwise they would be cleared'), which is critical operational guidance not captured in annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While well-structured with clear sections and examples, the description is quite lengthy (over 800 words) with extensive technical details. Some information could potentially be streamlined, though most content appears valuable for this complex tool. The purpose is front-loaded effectively.

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

Completeness5/5

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

Given the tool's high complexity (9 parameters, nested objects, 44% schema coverage, no output schema), the description provides comprehensive context. It covers connector types, SSL settings, update warnings, parameter interactions, and complete examples, making it sufficiently complete for an agent to understand and use this tool effectively.

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

Parameters5/5

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

With only 44% schema description coverage, the description compensates excellently by providing detailed parameter semantics. It explains connectorType-specific configurations (REST, SOAP, SAP RFC), sslSettings with trustType meanings, and provides complete JSON examples that clarify how parameters interact and should be structured, far exceeding what the sparse schema provides.

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 explicitly states the tool's purpose as 'create new connectors' and 'modify existing connectors', providing specific verbs and resources. It clearly distinguishes this from sibling tools like connector-delete and connector-call-update by focusing on creation and modification rather than deletion or testing.

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 clear guidance on when to use this tool for creation vs. update scenarios, including the important warning about fetching existing resources first when updating. However, it doesn't explicitly contrast when to use this versus alternatives like connector-wizard-rfc-create or other sibling tools, which prevents a perfect score.

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