Skip to main content
Glama

Prepare For New Conversation

prepare_for_new_conversation
Read-only

Reset conversation context to start fresh interactions, clearing previous chat history and settings on user request.

Instructions

Instructions for preparing for a new conversation. This tool should only be called on explicit user request.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • PrepareForNewConversationTool class defines the tool handler. Its apply() method executes the tool logic by calling the prompt factory to generate the preparation instructions for a new conversation.
    class PrepareForNewConversationTool(Tool):
        """
        Provides instructions for preparing for a new conversation (in order to continue with the necessary context).
        """
    
        def apply(self) -> str:
            """
            Instructions for preparing for a new conversation. This tool should only be called on explicit user request.
            """
            return self.prompt_factory.create_prepare_for_new_conversation()
  • PromptFactory method that renders the prompt template named 'prepare_for_new_conversation', used by the tool handler.
    def create_prepare_for_new_conversation(self) -> str:
        return self._render_prompt("prepare_for_new_conversation", locals())
  • ToolRegistry automatically discovers and registers all Tool subclasses (including PrepareForNewConversationTool) by iterating subclasses in serena.tools package.
    for cls in iter_subclasses(Tool):
        if not any(cls.__module__.startswith(pkg) for pkg in tool_packages):
            continue
        is_optional = issubclass(cls, ToolMarkerOptional)
        name = cls.get_name_from_cls()
        if name in self._tool_dict:
            raise ValueError(f"Duplicate tool name found: {name}. Tool classes must have unique names.")
        self._tool_dict[name] = RegisteredTool(tool_class=cls, is_optional=is_optional, tool_name=name)
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe, non-destructive operation. The description adds no behavioral context beyond what annotations provide, such as what 'preparing' entails or any side effects. However, it doesn't contradict annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two short sentences with zero wasted words. It's appropriately sized and front-loaded, though the first sentence is uninformative. Every sentence serves a purpose: the first states the tool's name, and the second provides critical usage guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has zero parameters, annotations covering safety, and an output schema (which means return values are documented elsewhere), the description is minimally adequate. However, it fails to explain what 'preparing for a new conversation' actually means or what the tool does, leaving a significant gap in understanding its purpose.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, and schema description coverage is 100%. With no parameters to document, the description doesn't need to compensate for any gaps. The baseline for zero parameters is 4, as there's nothing to explain beyond the empty schema.

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

Purpose2/5

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

The description 'Instructions for preparing for a new conversation' is a tautology that restates the tool's name/title without specifying what the tool actually does. It lacks a clear verb+resource combination and doesn't distinguish this tool from its many siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states 'This tool should only be called on explicit user request,' providing clear when-to-use guidance. This is a strong, unambiguous usage rule that helps the agent avoid inappropriate invocations.

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/oraios/serena'

If you have feedback or need assistance with the MCP directory API, please join our Discord server