Skip to main content
Glama

memory_log_conversation_append

Append additional text to the current conversation log entry when responses exceed single-call limits, enabling complete recording of extended AI interactions.

Instructions

Append more text to the last Agent section in today's journal.

Use after memory_log_conversation() when your full reply did not fit in one call. Can be called multiple times; each chunk is appended to the same turn.

Args: agent_response_chunk: Next part of your reply to append (no truncation).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_response_chunkYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The `memory_log_conversation_append` tool handler definition and implementation. It appends text to the last agent turn in the journal.
    @mcp.tool()
    async def memory_log_conversation_append(agent_response_chunk: str) -> str:
        """Append more text to the last Agent section in today's journal.
    
        Use after memory_log_conversation() when your full reply did not fit in one
        call. Can be called multiple times; each chunk is appended to the same turn.
    
        Args:
            agent_response_chunk: Next part of your reply to append (no truncation).
        """
        journal_dir = _get_journal_dir()
        ok = append_agent(journal_dir, agent_response_chunk)
        if ok:
            return "Appended to last conversation turn."
        return "No conversation turn found today; call memory_log_conversation first."
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It effectively discloses key behaviors: it appends to 'today's journal', maintains 'the same turn' across multiple calls, and guarantees 'no truncation'. Missing minor details like error cases if no previous section exists.

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

Conciseness5/5

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

Three efficient sentences/stanzas: first defines the action, second explains the workflow timing and multi-call behavior, third documents the parameter. No wasted words; information is front-loaded with the core action in the first sentence.

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

Completeness4/5

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

Given the tool has only one parameter and an output schema exists (so return values need not be described), the description is complete. It adequately explains the journaling workflow, chunking mechanism, and parameter semantics. Could be improved by mentioning error states or auth requirements.

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?

Schema coverage is 0% (no property descriptions in the JSON schema). The description compensates by documenting the parameter in the Args section, explaining it is the 'Next part of your reply' and adding the 'no truncation' constraint which is not inferable from the schema type alone.

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

Purpose5/5

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

Description states a specific action ('Append more text') on a specific resource ('the last Agent section in today's journal'). It clearly distinguishes this tool from sibling 'memory_log_conversation' by explaining this is for continuation/appending when a reply doesn't fit in one call.

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?

Explicitly states when to use ('Use after memory_log_conversation() when your full reply did not fit in one call') and includes repetition guidance ('Can be called multiple times'). It clearly references the sibling tool as the prerequisite/primary alternative.

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/liuhao6741/openclaw-memory'

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