Skip to Content

Anthropic Claude (Beta) Register Tools activity

Introduction

An Anthropic Claude (Beta) Register Tools activity, using its Anthropic Claude (Beta) connection, registers tools for use with Claude models and is intended to be used as a source to provide data in an operation. Tool schemas can be sourced from the MCP Client connector's List Tools activity or provided directly through the request transformation as custom function definitions.

When the operation runs, Jitterbit stores the registered tool schemas in memory on the private agent. Any operation chained to run after this one automatically has access to those schemas when it calls the LLM. You do not need to capture the Register Tools response or pass the tool definitions explicitly to the subsequent Prompt operation.

Important

To use the Register Tools activity, you must use a private agent.

Note

For beta access and to provide feedback, contact the Jitterbit Product Team.

Create an Anthropic Claude (Beta) Register Tools activity

An instance of an Anthropic Claude (Beta) Register Tools activity is created from an Anthropic Claude (Beta) connection using its Register Tools activity type.

To create an instance of an activity, drag the activity type to the design canvas or copy the activity type and paste it on the design canvas. For details, see Creating an activity instance in Component reuse.

An existing Anthropic Claude (Beta) Register Tools activity can be edited from these locations:

Configure an Anthropic Claude (Beta) Register Tools activity

Follow these steps to configure an Anthropic Claude (Beta) Register Tools activity:

Step 1: Enter a name and specify settings

In this step, provide a name for the activity, select a model, and specify a prompt and optional settings. Each user interface element of this step is described below.

Tip

Fields with a variable icon support using global variables, project variables, and Jitterbit variables. Begin either by typing an open square bracket [ into the field or by clicking the variable icon to display a menu listing existing variables to choose from.

  • Endpoint menu: If you have multiple endpoints of the same connector type configured, a menu at the top of the screen displays the current endpoint name. Click the menu to switch to a different endpoint. For more information, see Change the assigned endpoint in Configuration screens.

    • Edit endpoint: Appears when you hover over the current endpoint name. Click to edit the currently selected endpoint's connection configuration.

  • Name: Enter a name to identify the activity. The name must be unique for each Anthropic Claude (Beta) Register Tools activity and must not contain forward slashes / or colons :.

  • Chat ID: Optionally, enter a chat ID to retrieve context from a previous conversation.

  • Choose option: Specify the model selection method, either List all models or Enter model identifier.

  • List all models: Select this option to choose from a list of supported Claude models:

    • Select a model: This section displays models available for the Anthropic Claude (Beta) endpoint.

      • Selected model: After a model is selected, it is listed here.

      • Search: Enter any column's value into the search box to filter the list of models. The search is not case-sensitive. If models are already displayed within the table, the table results are filtered in real time with each keystroke. To reload models from the endpoint when searching, enter search criteria and then refresh, as described below.

      • Refresh: Click the refresh icon or the word Refresh to reload models from the Anthropic Claude (Beta) endpoint. This may be useful if models have been updated. This action refreshes all metadata used to build the table of models displayed in the configuration.

      • Selecting a model: Within the table, click anywhere on a row to select a model. Only one model can be selected. The following information is available for each model:

        • Display Name: The display name of the model.

        • ID: The model ID used in API requests.

        • Released: The release date of the model.

      Tip

      If the table does not populate with available models, the Anthropic Claude (Beta) connection may not be successful. Ensure you are connected by reopening the connection and retesting the credentials.

      Alternatively, the model can be specified in the Model ID field or provided in the request transformation. If a model is specified in multiple places, this order of precedence is followed:

      1. A model provided in the request transformation overrides all fields below.
      2. A model specified in the Model ID field overrides the remaining field below, even if List all models is selected.
      3. A model selected in the Select a model list has the least precedence.

  • Enter model identifier: Select this option to manually enter the ID of a Claude model.

    • Model ID: Enter the model ID.

  • Prompt: Enter the text to prompt the model with.

  • Optional settings: Click to expand additional optional settings:

    • Max Output Tokens: Enter the maximum number of tokens to generate in the response. The default is 2000. The maximum value depends on the selected model. Refer to the Anthropic models overview for per-model output token limits.

    • Enable extended thinking: Select to enable extended thinking, which allows the model to reason through complex problems before generating a response. This option is disabled by default.

      Important

      Extended thinking is not supported by all Claude models. If this option is enabled for a model that does not support it, Anthropic returns an error. Refer to the Anthropic models overview to confirm whether the selected model supports extended thinking.

      • Effort: Select the level of reasoning effort to apply. This setting is visible when Enable extended thinking is selected. The options are Low, Medium, High (default), Extra High, and Max. Higher effort levels allow more thorough reasoning but increase response time and token usage.

    • Enable Prompt Caching: Select to enable prompt caching, which allows the model to reuse previously processed content and reduce latency and cost for repeated prompt components. This option is disabled by default.

      • Cache Up To: Select the portion of the prompt to cache. This setting is visible when Enable Prompt Caching is selected. The options follow an additive hierarchy, where each level includes all content from the levels above it:

        • Tools: Caches only the tool definitions provided to the model.
        • Tools + System Prompt: (Default.) Caches tool definitions and the system prompt.
        • Tools + System + Chat History: Caches tool definitions, the system prompt, and the full chat history.

        For details, see the Anthropic prompt caching documentation.

    • Continue on error: Select to continue the activity execution if an error is encountered for a dataset in a batch request. If any errors are encountered, they are written to the operation log.

  • Save & Exit: If enabled, click to save the configuration for this step and close the activity configuration.

  • Next: Click to temporarily store the configuration for this step and continue to the next step. The configuration will not be saved until you click the Finished button on the last step.

  • Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.

Step 2: Review the data schemas

Any request or response schemas are displayed. Each user interface element of this step is described below.

  • Data schema: These data schemas are inherited by adjacent transformations and are displayed again during transformation mapping.

    Note

    Data supplied in a transformation takes precedence over the activity configuration.

    The Anthropic Claude (Beta) connector uses the Anthropic API. Refer to the API documentation for information on the schema nodes and fields.

  • Refresh: Click the refresh icon or the word Refresh to regenerate schemas from the Anthropic Claude (Beta) endpoint. This action also regenerates a schema in other locations throughout the project where the same schema is referenced, such as in an adjacent transformation.

  • Back: Click to temporarily store the configuration for this step and return to the previous step.

  • Finished: Click to save the configuration for all steps and close the activity configuration.

  • Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.

Next steps

After configuring an Anthropic Claude (Beta) Register Tools activity, complete the configuration of the operation by adding and configuring other activities, transformations, or scripts as operation steps. You can also configure the operation settings, which include the ability to chain operations together that are in the same or different workflows.

To complete a tool-calling workflow, chain a Prompt operation to run after this one. Because Jitterbit stores the tool schemas in memory on the private agent, the Prompt operation receives them automatically with no additional mapping required. To link the Prompt operation to this session's conversation history, capture the chatId from the Register Tools response and pass it to the Prompt activity in the request transformation.

Menu actions for an activity are accessible from the project pane and the design canvas. For details, see Activity actions menu in Connector basics.

Anthropic Claude (Beta) Register Tools activities can be used as a source with these operation patterns:

To use the activity with scripting functions, write the data to a temporary location and then use that temporary location in the scripting function.

When ready, deploy and run the operation and validate behavior by checking the operation logs.