Skip to main content
Glama
zebbern

agloop-mcp

by zebbern

agloop_append_log

Add structured execution records to track agent actions, phases, and statuses within the AgLoop framework for monitoring and management.

Instructions

Append a structured entry to the execution log. COORDINATOR ONLY.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agentYes
actionYes
phaseYes
statusYes
task_idNo
input_summaryNo
output_summaryNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The agloop_append_log tool handler, which utilizes the StateManager to append a structured log entry.
    def agloop_append_log(
        agent: str,
        action: str,
        phase: str,
        status: str,
        task_id: str = "",
        input_summary: str = "",
        output_summary: str = "",
    ) -> str:
        """Append a structured entry to the execution log. COORDINATOR ONLY."""
        _sm().append_log(
            agent=agent,
            action=action,
            phase=phase,
            status=status,
            task_id=task_id or None,
            input_summary=input_summary,
            output_summary=output_summary,
        )
        return json.dumps({"success": True})
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 the tool is 'COORDINATOR ONLY', hinting at permission requirements, but fails to describe other key traits like whether this is a write operation (implied by 'Append'), potential side effects, rate limits, or response format. This leaves significant gaps for a tool with 7 parameters.

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?

The description is extremely concise with only two short phrases, front-loading the core action and constraint. There is zero wasted language, making it highly efficient and easy to parse quickly.

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

Completeness2/5

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

Given the complexity (7 parameters, 4 required), lack of annotations, and 0% schema coverage, the description is incomplete. It doesn't explain parameter meanings, behavioral details, or output (though an output schema exists, which mitigates some gaps). For a tool with many undocumented inputs, more context is needed to be fully helpful.

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

Parameters1/5

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

Schema description coverage is 0%, meaning none of the 7 parameters are documented in the schema. The description does not add any meaning beyond the parameter names (e.g., it doesn't explain what 'agent', 'action', 'phase', or 'status' represent or their expected formats), failing to compensate for the lack of schema documentation.

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 verb ('Append') and resource ('structured entry to the execution log'), making the purpose specific and understandable. However, it doesn't explicitly differentiate this tool from sibling logging tools like 'agloop_get_logs' or 'agloop_search_logs', which prevents a perfect score.

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?

The description includes a usage constraint ('COORDINATOR ONLY'), which provides some context, but it lacks guidance on when to use this tool versus alternatives like 'agloop_search_logs' for reading logs or other sibling tools. No explicit when-not-to-use scenarios or prerequisites are mentioned.

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