Overview

Description

Intended Use

This validator validates that a generated output is polite.

Requirements

Dependencies:
- litellm
- guardrails-ai>=0.4.0
API keys: Set your LLM provider API key as an environment variable which will be used by litellm to authenticate with the LLM provider. For more information on supported LLM providers and how to set up the API key, refer to the LiteLLM documentation.

Installation

$ guardrails hub install hub://guardrails/politeness_check

Usage Examples

Validating string output via Python

In this example, we’ll test that a generated sentence is polite.

# Import Guard and Validator
from guardrails import Guard
from guardrails.hub import PolitenessCheck

# Setup Guard
guard = Guard().use(
    PolitenessCheck,
    llm_callable="gpt-3.5-turbo",
    on_fail="exception",
)

res = guard.validate(
    "Hello, I'm Claude 3, and am here to help you with anything!",
    metadata={"pass_on_invalid": True},
)  # Validation passes
try:
    res = guard.validate(
        "Are you insane? I'm not going to answer that!"
    )  # Validation fails because this response is impolite
except Exception as e:
    print(e)

Output:

Validation failed for field with errors: The LLM says 'No'. The validation failed.

API Reference

__init__(self, llm_callable="gpt-3.5-turbo", on_fail="noop")

Initializes a new instance of the Validator class.

Parameters:

llm_callable (str): The LLM string for LiteLLM to use for validation. Defaults to gpt-3.5-turbo.
on_fail (str, Callable): The policy to enact when a validator fails. If str, must be one of reask, fix, filter, refrain, noop, exception or fix_reask. Otherwise, must be a function that is called when the validator fails.

__call__(self, value, metadata={}) -> ValidationResult

Validates the given value using the rules defined in this validator, relying on the metadata provided to customize the validation process. This method is automatically invoked by guard.parse(...), ensuring the validation logic is applied to the input data.

Note:

This method should not be called directly by the user. Instead, invoke guard.parse(...) where this method will be called internally for each associated Validator.
When invoking guard.parse(...), ensure to pass the appropriate metadata dictionary that includes keys and values required by this validator. If guard is associated with multiple validators, combine all necessary metadata into a single dictionary.