Skip to main content
Glama
zebbern

agloop-mcp

by zebbern

agloop_get_logs

Retrieve execution logs from the AgLoop agent framework with filtering options for agent, task, or result limits to monitor and analyze workflow performance.

Instructions

Read execution log entries. Supports filtering by agent, task, and limiting results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
agentNo
task_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The 'agloop_get_logs' tool is defined as an MCP tool in 'src/agloop_mcp/server.py'. It acts as a handler that retrieves log entries from the 'StateManager'.
    def agloop_get_logs(
        limit: int = 0,
        agent: str = "",
        task_id: str = "",
    ) -> str:
        """Read execution log entries. Supports filtering by agent, task, and limiting results."""
        entries = _sm().get_logs(
            limit=limit or None,
            agent=agent or None,
            task_id=task_id or None,
        )
        return json.dumps([asdict(e) for e in entries], indent=2)
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a read operation and mentions filtering capabilities, but doesn't describe important behavioral aspects like pagination, sorting, default ordering, rate limits, authentication requirements, or what happens when no filters are applied. The description provides basic intent but lacks operational details.

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 at just two sentences with zero wasted words. It's front-loaded with the core purpose followed by key capabilities. Every word earns its place in this minimal but complete statement of function.

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 has an output schema (which handles return values), 3 parameters with 0% schema coverage, and no annotations, the description provides the minimum viable information: purpose and parameter scope. However, for a log retrieval tool with filtering capabilities, it should ideally explain more about the log structure, default behaviors, or relationship to sibling tools.

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?

With 0% schema description coverage, the schema provides no parameter documentation. The description mentions three filtering parameters (agent, task, limit) which aligns with the three parameters in the schema, giving basic semantic meaning. However, it doesn't explain parameter formats (e.g., what constitutes a valid task_id), the meaning of limit=0, or whether filters are AND/OR combinations.

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: 'Read execution log entries' specifies the verb (read) and resource (execution log entries). It distinguishes from siblings like 'agloop_append_log' (write) and 'agloop_search_logs' (search), but doesn't explicitly differentiate from other read tools like 'agloop_get_task' or 'agloop_get_state'.

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 implies usage context by mentioning filtering capabilities ('Supports filtering by agent, task, and limiting results'), suggesting when this tool might be appropriate. However, it doesn't explicitly state when to use this vs. alternatives like 'agloop_search_logs' or provide any exclusion criteria or prerequisites.

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