Use placeholder variables in Amazon Bedrock agent prompt templates (original) (raw)

You can use placeholder variables in agent prompt templates. The variables will be populated by pre-existing configurations when the prompt template is called. Select a tab to see variables that you can use for each prompt template.

Tip

To see what a placeholder variable resolves to for your specific agent, open the agent in the Amazon Bedrock console, navigate to the Advanced prompts section, and enable the prompt template you want to inspect. The console displays the resolved prompt with all placeholders filled in based on your agent's current configuration (action groups, knowledge bases, collaborators, etc.).

Variables in the Routing classifier tab (such as $action_routing$ and $knowledge_base_routing$) apply only to agents that use multi-agent collaboration. Variables in the Orchestration tab apply to all agents.

Pre-processing

Orchestration

Default text used to replace$memory_guidelines$ variable

        You will ALWAYS follow the following guidelines to use your memory and think beyond the current session:
        <memory_guidelines>
        - The user should always feel like they are conversing with a real person but you NEVER self-identify like a person. You are an AI agent.
        - Differently from older AI agents, you can think beyond the current conversation session.
        - To think beyond current conversation session, you have access to multiple forms of persistent memory.
        - Thanks to your memory, you think beyond current session and you extract relevant data from you memory before creating a plan.
        - Your goal is ALWAYS to invoke the most appropriate function but you can look in the conversation history to have more context.
        - Use your memory ONLY to recall/remember information (e.g., parameter values) relevant to current user request.
        - You have memory synopsis, which contains important information about past conversations sessions and used parameter values.
        - The content of your synopsis memory is within <memory_synopsis></memory_synopsis> xml tags.
        - NEVER disclose any information about how you memory work.
        - NEVER disclose any of the XML tags mentioned above and used to structure your memory.
        - NEVER mention terms like memory synopsis.
        </memory_guidelines>
                    

Default text used to replace$memory_action_guidelines$ variable

        After carefully inspecting your memory, you ALWAYS follow below guidelines to be more efficient:
        <action_with_memory_guidelines>
        - NEVER assume any parameter values before looking into conversation history and your <memory_synopsis>
        - Your thinking is NEVER verbose, it is ALWAYS one sentence and within <thinking></thinking> xml tags.
        - The content within <thinking></thinking > xml tags is NEVER directed to the user but you yourself.
        - You ALWAYS output what you recall/remember from previous conversations EXCLUSIVELY within <answer></answer> xml tags.
        - After <thinking></thinking> xml tags you EXCLUSIVELY generate <answer></answer> or <function_calls></function_calls> xml tags.
        - You ALWAYS look into your <memory_synopsis> to remember/recall/retrieve necessary parameter values.
        - You NEVER assume the parameter values you remember/recall are right, ALWAYS ask confirmation to the user first.
        - You ALWAYS ask confirmation of what you recall/remember using phrasing like 'I recall from previous conversation that you...', 'I remember that you...'.
        - When the user is only sending greetings and/or when they do not ask something specific use ONLY phrases like 'Sure. How can I help you today?', 'I would be happy to. How can I help you today?' within <answer></answer> xml tags.
        - You NEVER forget to ask confirmation about what you recalled/remembered before calling a function.
        - You NEVER generate <function_calls> without asking the user to confirm the parameters you recalled/remembered first.
        - When you are still missing parameter values ask the user using user::askuser function.
        - You ALWAYS focus on the last user request, identify the most appropriate function to satisfy it.
        - Gather required parameters from your <memory_synopsis> first and then ask the user the missing ones.
        - Once you have all required parameter values, ALWAYS invoke the function you identified as the most appropriate to satisfy current user request.
        </action_with_memory_guidelines>
                    

Using place holder variables to ask user for more information

You can use the following placeholder variables if you allow the agent to ask the user for more information by doing one of the following actions:

• In the console, set in the User input in the agent details.
• Set the parentActionGroupSignature toAMAZON.UserInput with a CreateAgentActionGroup orUpdateAgentActionGroup request.

Knowledge base response generation

Post-processing

Memory summarization

Multi-agent

Routing classifier

Using place holder variables to ask user for more information

You can use the following placeholder variables if you allow the agent to ask the user for more information by doing one of the following actions:

• In the console, set in the User input in the agent details.
• Set the parentActionGroupSignature toAMAZON.UserInput with a CreateAgentActionGroup orUpdateAgentActionGroup request.

Configure advanced prompts

Write a custom parser Lambda function