Skip to main content
Glama
zebbern

agloop-mcp

by zebbern

agloop_get_task

Retrieve task details including status, dependencies, acceptance criteria, and result log by providing a task ID for monitoring and management.

Instructions

Get details for a single task by ID. Returns task status, dependencies, acceptance criteria, and result log.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler for the tool 'agloop_get_task' is defined here as a decorator-wrapped function that uses the StateManager to retrieve task details.
    def agloop_get_task(task_id: str) -> str:
        """Get details for a single task by ID. Returns task status, dependencies, acceptance criteria, and result log."""
        task = _sm().get_task(task_id)
        if not task:
            return json.dumps({"error": f"Task '{task_id}' not found"})
        return json.dumps(asdict(task), indent=2)
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the return fields (status, dependencies, acceptance criteria, result log), which adds some context, but fails to cover critical aspects like error handling (e.g., what happens if the task ID is invalid), performance characteristics, or authentication requirements. For a read operation without annotations, 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.

Conciseness5/5

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

The description is extremely concise and front-loaded, consisting of two efficient sentences that directly state the action and return values. Every word earns its place, with no redundant or vague phrasing, making it easy to parse quickly.

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's low complexity (single parameter, no nested objects) and the presence of an output schema (which likely details the return structure), the description is reasonably complete. It covers the core purpose and key return fields, though it lacks usage guidelines and deeper behavioral context, which are less critical for a simple read operation with structured output.

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

Parameters3/5

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

The input schema has 0% description coverage, so the description must compensate. It implies the parameter 'task_id' is used to identify a task, but doesn't specify format, constraints, or examples. Since there's only one parameter, the baseline is higher, but the description adds minimal value beyond what's obvious from the schema's title ('Task Id').

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 ('Get details') and resource ('single task by ID'), making the purpose specific and understandable. It distinguishes from siblings like 'agloop_list_tasks' (which lists multiple tasks) and 'agloop_get_next_task' (which retrieves a different type of task). However, it doesn't explicitly mention how it differs from 'agloop_get_state' or 'agloop_get_plan', which might also retrieve task-related data, leaving some ambiguity.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, such as needing a valid task ID, or compare it to siblings like 'agloop_get_next_task' for workflow progression or 'agloop_list_tasks' for overviews. This lack of context could lead to misuse in complex scenarios.

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