Skip to main content
Glama

agent_state_update_state

Update the agent's current state description to track progress and maintain continuity across sessions by saving state to a specified directory.

Instructions

Update the agent state file, replacing its contents.

Args: directory: Absolute path to the GitHub worktree or repository directory where the state file should be saved state: The current state description of what the agent is trying to do

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
directoryYes
stateYes

Implementation Reference

  • main.py:80-92 (handler)
    The `agent_state_update_state` tool is defined here as an MCP tool using `@mcp.tool()`. It takes a `directory` and `state` string, validates the directory using `get_state_file`, and writes the state to `.agent-state.txt`.
    @mcp.tool()
    def agent_state_update_state(directory: str, state: str) -> None:
        """Update the agent state file, replacing its contents.
    
        Args:
            directory: Absolute path to the GitHub worktree or repository directory
                       where the state file should be saved
            state: The current state description of what the agent is trying to do
    
        """
        state_file = get_state_file(directory)
        state_file.write_text(state, encoding="utf-8")
Behavior3/5

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

With no annotations provided, the description carries the full burden. It successfully discloses the destructive replacement behavior, but omits other critical behavioral traits such as whether it creates the file/directory if missing, atomicity guarantees, or error conditions.

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 efficiently structured with a one-sentence purpose statement followed by a clear Args block. There is minimal redundancy, though the Args formatting consumes space that could be in the schema itself.

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 lack of annotations, output schema, and schema descriptions, the description provides adequate but incomplete coverage. It misses error handling behavior, return values (success/failure indicators), and file format details that would be necessary for robust agent operation.

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

Parameters5/5

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

With 0% schema description coverage, the Args block fully compensates by providing detailed semantics: 'directory' is clarified as an absolute path to a GitHub worktree/repository, and 'state' is explained as the current state description of the agent's task. This adds complete meaning beyond the raw schema types.

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

Purpose4/5

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

The description clearly states the tool updates the agent state file and explicitly notes the destructive 'replacing its contents' behavior. This distinguishes it from sibling load_state (read) and log_message (likely append) operations, though it doesn't explicitly name those alternatives.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus the sibling load_state or log_message tools, nor any mention of prerequisites (e.g., directory must exist) or idempotency considerations.

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/tianhuil/agent-state'

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