Skip to main content
Glama
zebbern

agloop-mcp

by zebbern

agloop_create_checkpoint

Save the current state for recovery in the AgLoop agent framework. Use this tool to create checkpoints that preserve agent states, tasks, and execution logs.

Instructions

Create a checkpoint of the current state for recovery. COORDINATOR ONLY.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelNo
triggerNomanual

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Implementation of the agloop_create_checkpoint tool handler.
    @mcp.tool()
    def agloop_create_checkpoint(
        label: str = "",
        trigger: str = "manual",
    ) -> str:
        """Create a checkpoint of the current state for recovery. COORDINATOR ONLY."""
        result = _sm().create_checkpoint(
            label=label or None,
            trigger=trigger,
        )
        if not result:
            return json.dumps({"error": "Failed to create checkpoint"})
        return json.dumps(
            {"id": result["id"], "label": result["label"], "timestamp": result["timestamp"]},
Behavior2/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 of behavioral disclosure. It mentions 'COORDINATOR ONLY', which hints at authorization needs, but lacks details on permissions, whether the checkpoint is reversible, rate limits, or what happens upon creation. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 brief and front-loaded with the main purpose, using only two short phrases. It avoids unnecessary words, but could be slightly more structured by separating the role restriction into a clearer guideline. Overall, it's efficient with minimal waste.

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's complexity (a mutation operation for recovery), lack of annotations, and an output schema (which reduces the need to describe return values), the description is somewhat incomplete. It covers the basic purpose and a role restriction but misses details on parameters, behavioral traits, and usage context, making it adequate but with clear gaps.

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

Parameters2/5

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

The input schema has 2 parameters with 0% description coverage, and the tool description doesn't mention or explain the parameters (label and trigger). This fails to compensate for the low schema coverage, leaving parameters undocumented and their semantics unclear beyond the schema's basic titles and defaults.

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's purpose with a specific verb ('Create') and resource ('checkpoint of the current state for recovery'), making it understandable. However, it doesn't explicitly differentiate from sibling tools like 'agloop_get_state' or 'agloop_update_task', which might also involve state operations, so it doesn't reach the highest score.

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

Usage Guidelines3/5

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

The description provides some context with 'COORDINATOR ONLY', implying usage is restricted to a specific role, but it doesn't offer explicit guidance on when to use this tool versus alternatives like 'agloop_get_state' for reading state or other tools for recovery purposes. This leaves usage somewhat implied rather than fully clarified.

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/zebbern/agloop-mcp'

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