Skip to main content
Glama

connector-wizard-rfc-create

Destructive

Create RFC connector calls for SAP system functions. Select function names to generate connector calls that enable integration with remote SAP systems.

Instructions

Create one or more calls for an RFC connector using the wizard

The RFC connector requires calls to refer to existing functions on the remote SAP system. To find available functions, use the resource template simplifier://connector-wizard/{connectorName}/search/{term}/{page}. Select the desired function names and pass them to this tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
connectorNameYesName of the RFC Connector to add calls to
rfcFunctionNamesYesNames of the SAP system's functions for which to create connector calls

Implementation Reference

  • The main execution handler for the 'connector-wizard-rfc-create' tool. It fetches details for RFC functions, prepares payload, and creates connector calls using the Simplifier client.
    async ({connectorName, rfcFunctionNames}) => {
      return wrapToolResult(`create ${rfcFunctionNames.length} connector calls using the RFC connector wizard`, async () => {
        const trackingKey = trackingToolPrefix + toolNameConnectorWizardRfcCreate;
    
        // required, so that the functions are "persisted" in Simplifier
        await simplifier.viewRFCFunctions(connectorName, rfcFunctionNames, trackingKey);
    
        const details = await simplifier.rfcWizardGetCallDetails(connectorName, rfcFunctionNames)
        const descriptions: {[k: string]: string} = {}
        const newNames: {[k: string]: string} = {}
        for(const func of rfcFunctionNames) {
          const match = details.calls.find(callDetails => callDetails.call.nameNonTechnicalized === func);
          if(!match) {
            throw new Error(`Details for function ${func} could not be retrieved`);
          }
          descriptions[func] = match.call.description;
          newNames[func] = match.call.name;
    
        }
        const payload: RFCWizardCreateCallsPayload = {
          callsRfc: rfcFunctionNames,
          descriptions: descriptions,
          newNames: newNames,
        }
    
        await simplifier.rfcWizardCreateCalls(connectorName, payload);
        return payload;
      });
    }
  • Zod input schema defining parameters: connectorName (string) and rfcFunctionNames (array of strings).
    inputSchema: {
      connectorName: z.string().describe(`Name of the RFC Connector to add calls to`),
      rfcFunctionNames: z.array(z.string()).describe(`Names of the SAP system's functions for which to create connector calls`),
    },
  • Tool name constant and full server.registerTool call registering the tool with description, schema, annotations, and handler.
      const toolNameConnectorWizardRfcCreate = "connector-wizard-rfc-create"
      server.registerTool(toolNameConnectorWizardRfcCreate,
        {
          description: `# Create one or more calls for an RFC connector using the wizard
    
    The RFC connector requires calls to refer to existing functions on the remote SAP system. To find available functions,
    use the resource template \`simplifier://connector-wizard/{connectorName}/search/{term}/{page}\`. Select the desired
    function names and pass them to this tool.
        `,
          inputSchema: {
            connectorName: z.string().describe(`Name of the RFC Connector to add calls to`),
            rfcFunctionNames: z.array(z.string()).describe(`Names of the SAP system's functions for which to create connector calls`),
          },
          annotations: {
            title: "Create RFC connector calls using the call wizard",
            readOnlyHint: false,
            destructiveHint: true,
            idempotentHint: false,
            openWorldHint: true
          },
        },
        async ({connectorName, rfcFunctionNames}) => {
          return wrapToolResult(`create ${rfcFunctionNames.length} connector calls using the RFC connector wizard`, async () => {
            const trackingKey = trackingToolPrefix + toolNameConnectorWizardRfcCreate;
    
            // required, so that the functions are "persisted" in Simplifier
            await simplifier.viewRFCFunctions(connectorName, rfcFunctionNames, trackingKey);
    
            const details = await simplifier.rfcWizardGetCallDetails(connectorName, rfcFunctionNames)
            const descriptions: {[k: string]: string} = {}
            const newNames: {[k: string]: string} = {}
            for(const func of rfcFunctionNames) {
              const match = details.calls.find(callDetails => callDetails.call.nameNonTechnicalized === func);
              if(!match) {
                throw new Error(`Details for function ${func} could not be retrieved`);
              }
              descriptions[func] = match.call.description;
              newNames[func] = match.call.name;
    
            }
            const payload: RFCWizardCreateCallsPayload = {
              callsRfc: rfcFunctionNames,
              descriptions: descriptions,
              newNames: newNames,
            }
    
            await simplifier.rfcWizardCreateCalls(connectorName, payload);
            return payload;
          });
        }
      );
Behavior3/5

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

Annotations indicate destructiveHint=true, readOnlyHint=false, openWorldHint=true, and idempotentHint=false, covering key behavioral traits. The description adds context about the wizard process and prerequisites, but doesn't disclose additional behavioral details like rate limits, auth needs, or specific destructive effects beyond what annotations imply. No contradiction with annotations exists.

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 appropriately sized and front-loaded, starting with the main purpose and followed by concise usage steps. Every sentence adds value without redundancy, making it efficient and well-structured for quick understanding.

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?

Given the tool's complexity (destructive creation with prerequisites), annotations cover safety and behavior well, and schema coverage is complete. The description adds necessary context about the wizard and resource template, compensating for the lack of output schema. It's mostly complete but could briefly mention expected outcomes or error handling.

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%, with clear descriptions for both parameters. The description adds semantic context by explaining that connectorName refers to an RFC Connector and rfcFunctionNames are SAP system functions, but this mostly reinforces the schema without providing significant extra meaning like format examples or constraints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool creates calls for an RFC connector using a wizard, specifying the verb ('create'), resource ('calls'), and context ('RFC connector'). It distinguishes from siblings like connector-call-delete or connector-call-update by focusing on creation via a wizard, though it doesn't explicitly contrast with all alternatives.

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 context on when to use this tool: after finding available functions via a specific resource template and selecting desired function names. It implies prerequisites but doesn't explicitly state when not to use it or name alternatives among siblings, though the context is sufficient for typical usage.

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