Skip to main content
Glama
zebbern

agloop-mcp

by zebbern

agloop_get_plan

Retrieve the current plan file contents (plan.yaml or plan.md) to monitor and manage agent tasks and execution within the AgLoop framework.

Instructions

Read the current plan (plan.yaml or plan.md). Returns raw file contents.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The MCP tool handler for "agloop_get_plan", which reads the plan from the StateManager and returns the contents or an error message.
    @mcp.tool()
    def agloop_get_plan() -> str:
        """Read the current plan (plan.yaml or plan.md). Returns raw file contents."""
        plan = _sm().get_plan()
        if not plan:
            return json.dumps({"error": "No plan found"})
        return plan
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 reads files and returns raw contents, which is basic behavioral info. However, it lacks details on permissions, error handling, or file location, leaving gaps in transparency for a read operation.

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 front-loaded and concise, using only one sentence with zero waste. It efficiently states the action and outcome without unnecessary details, making it easy to parse.

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 has 0 parameters, an output schema exists, and no annotations, the description is mostly complete for a simple read operation. It specifies file types and return format, but could benefit from more context on when to use it versus siblings, slightly reducing completeness.

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

Parameters4/5

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

The input schema has 0 parameters with 100% coverage, so no parameter info is needed. The description adds value by specifying the file types (plan.yaml or plan.md), which isn't in the schema, but this is minimal since parameters are absent. Baseline is high due to no parameters.

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 ('Read') and resource ('current plan'), specifying the file types (plan.yaml or plan.md). However, it does not explicitly differentiate from siblings like 'agloop_get_state' or 'agloop_get_task', which might also retrieve data, leaving some ambiguity about scope.

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?

No guidance is provided on when to use this tool versus alternatives, such as 'agloop_get_state' or 'agloop_get_task'. The description implies it's for reading plan files, but it lacks explicit context or exclusions, leaving usage unclear relative to siblings.

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