Skip to main content
Version: v1.7.5-5 🚧

Agent tool configuration

Administrator Guide

This page provides integration details, configuration parameters, and requirements for all built-in agent tools available in Enterprise h2oGPTe. It is intended for administrators (DevOps, IT, MLOps, or platform engineers) who deploy, manage, or secure Enterprise h2oGPTe in production or enterprise environments.

Here you'll find:

  • Tool-by-tool configuration variables and deployment requirements
  • Default and optional settings, including cloud services and external API keys
  • Hardware and dependency notes (e.g., GPU requirements, tokens/credentials needed)
  • Best practices for enabling or restricting tools based on your organization's compliance, security, or data-access policies

Before onboarding end users or exposing agent capabilities, review this guide to ensure your environment is correctly configured and all necessary prerequisites—such as external integrations, cloud credentials, or on-prem services—are in place.

Shared Agent Model Configuration: Administrators can configure a shared default language model for all agents in Enterprise h2oGPTe, setting a consistent default model across agent interactions. Users may still override this selection for individual conversations if needed.

Tool configuration requirements​

Enterprise h2oGPTe includes multiple built-in agent tools, each with specific requirements. Basic agent functionality is enabled by default, but many tools require additional configuration. Additionally, administrators can deploy custom tools to extend agent capabilities with organization-specific functionality.

  • Check the requirements for each tool you intend to use
  • Configure the necessary environment variables in your Helm deployment
  • Ensure any required external services or credentials are set up properly
  • Verify that hardware requirements (such as GPU for image generation) are met
  • Replace all <your-*-key> placeholders with actual keys/tokens
note

All configuration examples below are Helm chart configurations for administrators. Users will select and use tools through the h2oGPTe interface after administrators have properly configured them.

This basic agent configuration in your Helm chart enables several tools by default:

h2ogpt:
  config:
    externalLLM:
      secret:
        # Path to store OpenAI API logs
        H2OGPT_OPENAI_LOG_PATH: "/workspace/save/h2ogpt_openai/"

        # Path to cache Hugging Face transformer models
        TRANSFORMERS_CACHE: "/workspace/.cache"

Managing tools in the UI​

To view and manage agent tools in the Enterprise h2oGPTe interface:

  1. Click Agents in the main menu.
  2. Click the Tools tab to view the agent tools table.
  3. Use the Filter Agent Tools search box to search for tools by name.
  4. Use the Owner dropdown next to the search box to filter tools by owner. The options are All, Built-in, and Custom.
  5. Click the Reset button to reset key associations to admin-defined defaults or reset to system default settings.
Important

When creating custom tools, users can choose to enable the Enable by default option or toggle it from the Default column in the table. Tools enabled by default are automatically available to users when new agent chat sessions are created, ensuring faster setup and consistent tool availability across your organization.

The tools table displays all available tools with their configuration status, environment variables, and secret references.

Agent Tools Table

Tool actions​

Each tool row in the table has an actions menu (three dots) that provides the following options:

  • Assign Env Vars — Assign authentication keys to the tool's environment variables (see Assigning keys to tools).
  • Edit Tool — Edit the tool's name, description, system prompt, or code (custom tools only).
  • Select Sub-Tools — Select which sub-tools to expose for remote or local MCP tools. Not available for predefined API app or OAuth app tools.
  • Download Tool — Download the tool's source file. Available for Local MCP, Browser Action, and General Code tool types. You can download only tools that you own.
  • Delete Tool — Remove the tool from the system (custom tools only).

Tool actions menu

Predefined MCP tools​

Predefined MCP tools are curated, one-click connectors for popular external services. Examples include Slack, Snowflake, Teradata, PowerPoint, Hugging Face, N8N Workflow Builder, Playwright, and the h2oGPTe MCP Server — see the MCP server directory for detailed per-tool configuration. Unlike custom MCP tools, which require entering server details manually, predefined tools ship with their connection details, required/optional API keys, and available sub-tools already curated, so you can add them without writing any JSON configuration.

note

Predefined tools that use OAuth-based authentication instead of API keys appear under a separate OAuth Apps tab, alongside the default Tools tab shown below, and are managed through Connectors. The OAuth Apps tab only appears when your deployment has connectors enabled and at least one OAuth-based tool is available.

Browsing and adding predefined tools​

To browse and add a predefined tool, you need the List, add, and remove builtin MCPs permission, which is granted to all users by default:

  1. Click Agents in the main menu.

  2. Click the Tools tab.

  3. Click Browse Tools to open the Predefined MCP Tools dialog.

    Open the Predefined MCP Tools dialog

  4. Click a tool card to view its details.

    The Predefined MCP Tools dialog

    note

    The Add Predefined Tool button shown above is only visible to administrators — see Managing predefined tools (administrators).

  5. Review the tool's description, developer, required and optional API keys, and its Available Sub-tools. Available Sub-tools lists the functions the underlying MCP server exposes — for example, a Slack tool's sub-tools include conversations_history, conversations_add_message, and reactions_add. The detail view also shows any per-key setup hints, links to the provider's website, documentation, and privacy policy, and the tool's connector command.

    Tool description

  6. Click Configure & Add:

    • If the tool requires API keys or configuration files, a dialog prompts you to select an existing authentication key for each required or optional variable (and upload any required configuration files) before adding. You can also create a new private key inline from this dialog instead of selecting an existing one.
    • If the tool needs no keys or files, it is added immediately.

    Once added, the button changes to Added and is disabled.

  7. After you add a tool, it appears in the Tools table owned by you (the account that added it).

note

Sub-tool selection through Select Sub-Tools (see Tool actions) is not supported for predefined tools. All sub-tools remain enabled.

Managing predefined tools (administrators)​

Administrators can add, edit, and delete predefined tools available to users, and manage each tool's logo:

  1. Open the Predefined MCP Tools dialog as described above and select the Tools tab.

  2. Click Add Predefined Tool, optionally upload a logo (PNG, JPG, SVG, or WebP, max 10MB), and enter the tool configuration as JSON. Only the api_app tool type is supported.

    Required fields:

    {
      "name": "Custom Tool Name",
      "subtitle": "Tool subtitle",
      "type": "api_app",
      "developed_by": "Developer Name",
      "provider_url": "https://provider.com",
      "description": "Tool description",
      "subtools": ["subtool1", "subtool2"],
      "links": {
        "website": "https://website.com",
        "documentation": "https://docs.com",
        "privacy": "https://privacy.com"
      },
      "mcp_config_json": {
        "command": "npx",
        "args": ["-y", "custom-tool"],
        "env": {
          "API_KEY": "os.environ/API_KEY"
        },
        "tool_usage_mode": ["runner"]
      }
    }

    subtools lists the sub-tool (function) names the underlying MCP server exposes — these are the same names shown in the Available Sub-tools section of the tool detail view and used to populate Select Sub-Tools.

    note

    This JSON schema is closed: only the fields listed here are accepted. Any other top-level field, or any unrecognized sub-key inside links, api_keys, or an entry of files, is rejected with an "Unknown fields not allowed" error. tool_usage_mode is optional and defaults to ["runner", "creator"] if omitted. For each env entry, "os.environ/<NAME>" tells h2oGPTe to inject the named environment variable at runtime — replace <NAME> with the same variable name you list under api_keys.

    Optional fields (add any of these alongside the required fields above):

    FieldTypeDescription
    api_keys{ required: string[], optional: string[] }API key variable names for the tool
    is_files_neededbooleanWhether the tool requires config files
    filesarray of { file_hint, format }Config file definitions. Only validated when is_files_needed is true and the array is non-empty.
    promptsarrayPrompt templates
    resourcesarrayResource definitions
    optionsarrayAdditional tool options
    note

    The tool's internal ID is derived from name (lowercased, with spaces replaced by underscores). Reusing an existing tool's exact name updates that tool instead of creating a new one. If a different administrator's tool name normalizes to the same ID, adding or editing yours fails with an error.

  3. Click Add Tool to save. Refresh the page to see the new tool in the Tools tab.

  4. To edit an existing predefined tool, open its detail view and click Edit to update its JSON configuration, or use Upload Logo / Remove Logo to manage its icon. Editing replaces the tool's entire configuration, so include all fields, not just the ones you're changing. The Edit Tool action in the Tools table (see Tool actions) is not available for predefined tools — use the detail view in the Predefined MCP Tools dialog instead.

  5. To remove a predefined tool, open its detail view and click Delete.

note

Edit, Delete, Upload Logo, and Remove Logo are only available to the administrator who originally added the tool — not to other administrators, and not for tools that ship by default with Enterprise h2oGPTe.

Managing authentication keys in the UI​

The Authentication table displays all available keys with their secret reference names, descriptions, access levels, owners, creation dates, and update dates.

To view and manage authentication keys in the Enterprise h2oGPTe interface:

  1. Navigate to Agents in the main menu.
  2. Click the Authentication tab to view the authentication keys table.
  3. Use the search box to filter keys by secret reference name.
  4. Use the filter buttons to filter keys by ownership:
    • All Keys: Display all available keys
    • My Keys: Display only keys that you own
    • Other Keys: Display keys owned by other users in that workspace

Authentication Keys Table

Creating authentication keys​

To create a new authentication key:

  1. Click + Create Key on the Authentication page.
  2. In the Add Agent Key dialog, enter the required information:
    • Secret Reference Name: The name identifier for the key (required). This should match the environment variable name used in tool configurations.
    • Key Value: The actual API key, token, or credential value (required).
    • Description: An optional description of the key's purpose.
  3. Select the Key Type:
    • Private: The key is only available to you
    • Shared: The key is available to all users
  4. Click Add to create the key.

Add Agent Key Dialog

Assigning keys to tools​

After creating authentication keys, you must assign them to the tools that need them. To assign keys to tools:

  1. Navigate to Agents in the main menu.
  2. Click the Tools tab to view the agent tools table.
  3. Locate the tool you want to configure and click the actions menu (three dots) for that tool.
  4. Select Assign Environment Variable to open the Assign Environment Variable dialog.
  5. In the Assign Environment Variable dialog:
    • For tools with predefined environment variables, select a key from the dropdown for each required or optional environment variable.
    • For Python Coding and Shell Scripting tools, click + Add Environment Variable, enter the environment variable name, and select a key to add custom environment variables.
  6. Click Assign to save your key assignments.

Assign Environment Variable Dialog

note

Built-in keys are system-provided keys that are available by default and cannot be modified or deleted. Built-in keys can only be used with built-in tools, except for Python Coding and Shell Scripting tools, which only accept custom keys that you create.

caution

Store sensitive credentials securely and ensure proper access controls are in place. Private keys are only accessible to the key owner, while shared keys are accessible to all users in the organization. When administrators assign shared keys to tools, those key associations apply to all users in the workspace.

Session token forwarding​

Enterprise h2oGPTe automatically makes the authenticated user's session tokens available to agent tools as environment variables. Tools opt in by declaring the variable names; variables that are not declared are never added to the tool's environment, and any value already assigned by an operator is preserved.

Available session variables​

VariableWhat it carriesWhen to use
H2OGPT_SESSION_ACCESS_TOKENKeycloak access tokenCalls to h2oGPTe's own APIs
H2OGPT_SESSION_REFRESH_TOKENKeycloak refresh tokenAutonomous Keycloak token refresh
H2OGPT_SESSION_EXTERNAL_IDP_TOKENUpstream IdP access token (e.g. PingSSO, Azure AD)Calls to external services that reject Keycloak tokens
H2OGPT_SESSION_EXTERNAL_IDP_REFRESH_TOKENUpstream IdP refresh tokenAutonomous external IdP token refresh
caution

The external IdP refresh token has wider scope and a longer lifetime than the Keycloak token. Declare it only when the tool needs to refresh its own token during a single execution. For single-call tools, prefer H2OGPT_SESSION_EXTERNAL_IDP_TOKEN (access-only) and allow the agent to retry the tool on authentication failure.

External IdP token via Keycloak Identity Broker​

By default, only the Keycloak access and refresh tokens are available. In federated deployments, where users sign in via an upstream provider such as PingSSO or Azure AD, external services like Snowflake expect the upstream IdP's token, not the Keycloak token. To address this, Enterprise h2oGPTe can fetch the user's upstream IdP token from Keycloak's Identity Broker endpoint and forward it to tools that opt in by declaring H2OGPT_SESSION_EXTERNAL_IDP_TOKEN.

The feature activates only for federated users: those whose JSON Web Token (JWT) carries the identity_provider claim matching the configured alias. Users who authenticate directly through Keycloak (without federation) are unaffected. The feature is off by default.

Keycloak prerequisites​

warning

Before enabling this feature, confirm the following in the Keycloak admin console:

  1. Store Tokens must be enabled on the Identity Provider configuration (Identity Providers → your provider → Store Tokens: ON, Stored Tokens Readable: ON).
  2. The h2oGPTe Keycloak client must have the read-token role granted on the broker account client (Clients → h2ogpte → Service Accounts → Roles).

Helm configuration​

global:
  oidc:
    externalIdpBroker:
      enabled: true
      providerAlias: "<alias>"   # Keycloak IdP alias — e.g. pingsso, azure-ad, okta-corp

mux:
  config:
    sessionCacheKey: "<32+ char hex>"   # Shared across all mux replicas; also used by the Azure AD session cache

providerAlias is the alias assigned when creating the Identity Provider entry in the Keycloak admin console. The mechanism is provider-agnostic — PingSSO, Azure AD, Okta, and any other OIDC/OAuth2/SAML provider that Keycloak can broker work the same way.

For tool authors who want to receive these tokens, see Receiving session tokens in custom MCP tools.

Tools​

Data analysis capabilities​

  1. H2O Driverless AI Data Science: Build automated machine learning models and analyze data to generate actionable insights. This tool connects to H2O Driverless AI to run experiments, create predictions, and perform data analysis.

    Configure the tool:​

    h2ogpt:
      config:
        externalLLM:
          secret:
            ENABLE_DAI: "1"
            DAI_INSTANCE_TYPE: cloud
            DAI_CLIENT_ID: hac-platform-public
            DAI_ENGINE: <your-dai-engine>
            DAI_ENVIRONMENT: <your-dai-environment-url>
            DAI_TOKEN: <your-dai-token>
            DAI_TOKEN_ENDPOINT_URL: <your-token-endpoint-url>
            DAI_MAX_RUNTIME_MINUTES: "60"

    Configuration reference​

    ParameterTypeDeployment Type (Cloud/MC and On-Premises)Description
    ENABLE_DAIStringBothSet to "1" to enable Driverless AI integration
    DAI_INSTANCE_TYPEStringBothSpecify "cloud" or "onprem"
    DAI_CLIENT_IDStringCloud/MCClient ID for cloud instances. Default: hac-platform-public
    DAI_ENGINEStringCloud/MCEngine identifier for cloud deployments
    DAI_ENVIRONMENTStringCloud/MCCloud environment URL
    DAI_TOKENStringCloud/MCAuthentication token for cloud access
    DAI_TOKEN_ENDPOINT_URLStringCloud/MCToken endpoint URL for cloud authentication
    DAI_ADDRESSStringOn-PremisesServer address for on-premises installations
    DAI_USERNAMEStringOn-PremisesUsername for on-premises authentication
    DAI_PASSWORDStringOn-PremisesPassword for on-premises authentication
    DAI_MAX_RUNTIME_MINUTESIntegerBothRequired: Maximum runtime limit for experiments in minutes. Must be set to a positive integer value to prevent errors.

    How end users interact with the tool​

    Once configured, end users can interact with the H2O Driverless AI Data Science tool through natural language prompts. They don't need to write code directly. For example:

    • "Use Driverless AI to create a classification experiment with the Titanic dataset, targeting the 'Survived' column with accuracy setting 2"
    • "Run a regression experiment on my sales data with high interpretability"
    • "Create a DAI experiment with time setting 3 and accuracy setting 5"

    The agent automatically invokes the underlying tool function:

    # This code is executed automatically by the agent - not by end users
    from api_server.agent_tools.driverless_ai_data_science import driverless_ai_data_science

    driverless_ai_data_science(
        data="titanic.csv",
        dataset_name="titanic_test",
        target_column="Survived",
        task="classification",
        experiment_name="titanic_test_experiment",
        accuracy=2,
        time=2,
        interpretability=7
    )

    Secure your credentials​

    To securely access Driverless AI credentials:

    1. Navigate to Agents > Authentication in the Enterprise h2oGPTe UI.
    2. Create secure keys for DAI access.
    3. Assign the keys to the H2O Driverless AI Data Science tool.

    Access the credentials in your code:

    # Access credentials securely via environment variables
    enable_dai = os.getenv("ENABLE_DAI")
    dai_max_runtime = os.getenv("DAI_MAX_RUNTIME_MINUTES")
    Before you begin
    • Ensure your system has sufficient computational resources for experiments
    • For cloud instances: Verify authentication tokens and network connectivity
    • For on-premises: Confirm the Driverless AI (DAI) server is accessible from h2oGPTe
    • Set DAI_MAX_RUNTIME_MINUTES to a positive integer value (for example, 60) to prevent ValueError runtime errors. This parameter is required and cannot be empty.

  2. Python Coding: Execute Python code snippets for custom data computations, machine learning tasks, or to automate data preprocessing.

    Requirements:​

    • Enabled by default. No additional configuration required.

  3. Advanced Reasoning: Perform context-aware reasoning to enhance decision-making processes.

    Requirements:​

    • Requires models that support reasoning capabilities.

    • Configure in Helm chart:

      agent:
        enabled: true
        overrideConfig:
          visible_reasoning_models:
            - meta-llama/Llama-3.1-8B-Instruct
    tip

    To enhance reasoning depth and accuracy, you can set the AGENT_ACCURACY parameter to Max in your agent configuration. This setting may increase resource usage but improves the quality of context-aware reasoning.

Information retrieval and research​

  1. Scholar Papers Search: Locate scholarly papers, research articles, and academic content.

    Requirements:​

    • Requires the Internet Access tool to be enabled.

  2. Google search: Access Google's search capabilities to gather timely and accurate information.

    Requirements:​

    • Requires the Internet Access tool to be enabled.
    • Optional:
      • Configure the Google API key in Helm chart: 
        h2ogpt:
          config:
            externalLLM:
              secret:
                GOOGLE_API_KEY: <your-google-api-key>

  3. Bing search: Access Bing's search capabilities to gather timely and accurate information.

    Requirements:​

    • Requires the Internet Access tool to be enabled.
    • Optional:
      • Configure the Bing API key in Helm chart: 
        h2ogpt:
          config:
            externalLLM:
              secret:
                BING_API_KEY: <your-bing-api-key>

  4. Internet Access: Utilize general internet access for a wide range of tasks, from data retrieval to live updates.

    Requirements:​

    • Enabled by default. No additional configuration required.

  5. Wolfram|Alpha Math Science Search: Solve scientific and mathematical problems using the computational knowledge engine for complex computations.

    Requirements:​

    • Requires the Internet Access tool to be enabled.
    • Optional:
      • Configure the Wolfram|Alpha API key in Helm chart: 
        h2ogpt:
          config:
            externalLLM:
              secret:
                WOLFRAM_ALPHA_APPID: <your-wolfram-alpha-appid>

  6. Wikipedia Articles Search: Retrieve information from Wikipedia for learning or to support data analysis and research.

    Requirements:​

    • Requires the Internet Access tool to be enabled.

  7. Wayback Machine Search: Access archived versions of websites for research, historical context, or to reference past web content.

    Requirements:​

    • Requires the Internet Access tool to be enabled.

  8. Web Image Search: Find relevant images from the web to support visual analysis, presentations, or content creation.

    Requirements:​

    • Requires the Internet Access tool to be enabled.

  9. Browser Navigation: Automate web browsing tasks, including form filling, authentication, and complex web interactions across multiple platforms and services.

    Requirements:​

    • Requires the Internet Access tool to be enabled.
    • Enabled by default. No additional configuration required.
    • Optional API keys and credentials to configure in Helm chart for enhanced functionality: 
      h2ogpt:
        config:
          externalLLM:
            secret:
              # Search Engine APIs
              BING_API_KEY: <your-bing-api-key>
              SERPAPI_API_KEY: <your-serpapi-key>
              GOOGLE_API_KEY: <your-google-api-key>
              
              # AI Service APIs
              STT_OPENAI_API_KEY: <your-openai-stt-key>
              STT_OPENAI_BASE_URL: <your-openai-stt-base-url>
              STT_OPENAI_MODEL: <your-stt-model>
              ANTHROPIC_API_KEY: <your-anthropic-key>
              ANTHROPIC_BASE_URL: <your-anthropic-base-url>
              
              # Platform Credentials
              GOOGLE_USERNAME: <your-google-username>
              GOOGLE_PASSWORD: <your-google-password>
              GOOGLE_BIRTHDAY: <your-google-birthday>
              GOOGLE_HOME_ADDRESS: <your-google-home-address>
              GOOGLE_PHONE_NUMBER: <your-google-phone-number>
              
              # Data Platform APIs
              HUGGING_FACE_HUB_TOKEN: <your-huggingface-token>
              KAGGLE_API_KEY: <your-kaggle-api-key>
              KAGGLE_USERNAME: <your-kaggle-username>
              
              # RapidAPI Credentials
              RAPIDAPI_EMAIL: <your-rapidapi-email>
              RAPIDAPI_PASSWORD: <your-rapidapi-password>
    note

    Store sensitive credentials securely and ensure proper access controls are in place. Consider using environment-specific configurations for different deployment environments.

  10. Ask Question About Documents: Extract or query information from uploaded documents for detailed insights.

    Requirements:​

    • Enabled by default. No additional configuration required.

Content generation and transformation​

  1. Image Generation: Create custom images based on textual descriptions. Integrate image generation capabilities from different providers, including local models, OpenAI, Azure OpenAI, and Black Forest Labs.

    Requirements:​

    • Requires GPU in agent pod.
    • Shell Scripting tool must be enabled as a prerequisite.
    • Configuration in Helm chart: 
      h2ogpt:
        config:
          externalLLM:
            enabled: true
            secret:
              # Black Forest Labs Configuration
              BFL_API_KEY: <your-black-forest-labs-api-key>

              # OpenAI Configuration
              IMAGEGEN_OPENAI_BASE_URL: https://api.openai.com/v1
              IMAGEGEN_OPENAI_API_KEY: <your-openai-api-key>

              # Azure OpenAI Configuration
              AZURE_OPENAI_BASE_URL: openai.azure.com
              AZURE_OPENAI_API_KEY: <your-azure-openai-api-key>

      agent:
        enabled: true
        additionalConfig:
          function_api_key: <your-function-api-key>
          enforce_h2ogpt_api_key: false
          enforce_h2ogpt_ui_key: false
          enable_image: true
          visible_image_models:
            - "flux.1-schnell"  # Local model for image generation
            
            # Optional: Additional image generation models
            # Uncomment and replace with actual model names when using external providers
            # - "openai-model"  # OpenAI model
            # - "azure-model"   # Azure model

  2. Audio-Video Transcription: Convert spoken content from audio or video files into text.

    Requirements:​

    • Enabled by default. No additional configuration required.
    • Optional:
      • Configure the OpenAI base URL and API key for STT in Helm chart: 
        h2ogpt:
          config:
            externalLLM:
              secret:
                STT_OPENAI_BASE_URL: <your-stt-openai-base-url>
                STT_OPENAI_API_KEY: <your-stt-openai-api-key>
            additionalConfig:
              asr_model: "distil-whisper/distil-large-v3"  # Model for converting audio/video transcription
              enable_stt: true  # Enable speech-to-text for audio/video transcription
        note

        Ensure you have selected Agent Only as the Ingest Mode when uploading. See Ingestion modes.

  3. Convert Document to Text: Transform scanned or digital documents into editable text formats.

    Requirements:​

    • Enabled by default. No additional configuration required.

  4. Screenshot Webpage: Capture screenshots of webpages.

    Requirements:​

    • Requires the Internet Access tool to be enabled.

  5. Mermaid Chart-Diagram Renderer: Generate flowcharts and diagrams.

    Requirements:​

    • Enabled with the default configuration.

Automation and scripting​

  1. Shell Scripting: Automate system-level tasks to streamline operations.

    Requirements:​

    • Enabled by default. No additional configuration required.

Specialized AI features​

  1. RAG Text: Enhance text-based tasks with retrieval-augmented generation.

    Requirements:​

    • Uses default models in ModelLock.
    • Enabled by default. No additional configuration required.

  2. RAG Vision: Apply retrieval-augmented generation for vision-based tasks.

    Requirements:​

    • Uses default vision models in ModelLock.

Multimedia processing​

  1. Download Web Video: Download web videos.

    Requirements:​

    • Requires the Internet Access tool to be enabled.
    • Shell Scripting tool must be enabled as a prerequisite.

  2. Ask Question About Image: Query and analyze visual data.

    Requirements:​

    • Requires a vision model configured in ModelLock.

Software Development Tools​

  1. Aider Code Generation: Automatically generate code snippets to accelerate development tasks, particularly for data science and machine learning models.

    Requirements:​

    • Models are fetched from ModelLock.
    • No additional configuration required.

  2. GitHub: Integrates with the GitHub platform for version control, code repository browsing, and collaboration.

    Requirements:​

    • Requires configuring GITHUB_TOKEN as a secret in Helm chart: 
      h2ogpt:
        config:
          externalLLM:
            secret:
              GITHUB_TOKEN: <your-github-token>

  3. Evaluate Answer: Provides automated evaluation of responses generated by agents.

    Requirements:​

    • Enabled by default. No additional configuration required.

  4. SWEBench Evaluate Patch: Evaluates software patches by running automated tests, quality checks, and performance benchmarks.

    Requirements:​

    • Enabled by default. No additional configuration required.
note

To enable tools that require internet access, such as GitHub, Wikipedia Articles Search, Web Image Search, etc., administrators must ensure that the Internet Access tool is properly configured in their Helm deployment. Once configured by administrators, users can then select and use these tools through the Enterprise h2oGPTe interface.

Feedback