Skip to main content
Glama
zebbern

agloop-mcp

by zebbern

agloop_update_task

Update task status and result logs in AgLoop's agent framework. Automatically sets timestamps for coordinator users managing agent workflows.

Instructions

Update a task's status and/or result log. Auto-sets timestamps. COORDINATOR ONLY.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYes
statusNo
result_logNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The implementation of the `agloop_update_task` tool, which updates a task's status and result log, is defined as a tool handler decorated with `@mcp.tool()`.
    @mcp.tool()
    def agloop_update_task(
        task_id: str,
        status: str = "",
        result_log: str = "",
    ) -> str:
        """Update a task's status and/or result log. Auto-sets timestamps. COORDINATOR ONLY."""
        task = _sm().update_task(
            task_id,
            status=status or None,
            result_log=result_log or None,
        )
        if not task:
            return json.dumps({"error": f"Failed to update task '{task_id}'"})
        return json.dumps(asdict(task), indent=2)
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 discloses that the tool 'Auto-sets timestamps' (a behavioral trait) and has a 'COORDINATOR ONLY' restriction (implying auth needs), but doesn't cover other aspects like rate limits, error handling, or what happens to unspecified fields. This is adequate but has gaps for a mutation tool.

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—two sentences with zero waste. It front-loads the core action ('Update a task's status and/or result log') and efficiently adds key constraints ('Auto-sets timestamps. COORDINATOR ONLY.'), making every word earn its place.

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 a mutation tool with 3 parameters, 0% schema coverage, no annotations, but an output schema exists, the description is partially complete. It covers the purpose and some behavioral traits but lacks parameter details and doesn't fully compensate for the missing annotations. The output schema reduces the need to explain return values, but more context on usage and parameters would help.

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?

Schema description coverage is 0%, so the description must compensate. It mentions 'status and/or result log', which maps to two of the three parameters, but doesn't explain 'task_id' or provide any details on parameter formats, constraints, or interactions (e.g., that 'status' and 'result_log' are optional with defaults). The description adds minimal value beyond the schema.

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 'Update' and the resource 'task's status and/or result log', making the purpose specific. It distinguishes from siblings like 'agloop_get_task' (read) and 'agloop_append_log' (append-only), but doesn't explicitly name alternatives for partial updates.

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 coordinators. However, it doesn't specify when to use this vs. alternatives like 'agloop_append_log' for logs or 'agloop_set_phase' for other updates, leaving usage guidelines implied rather than explicit.

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