Skip to main content
Glama

romm_tasks

Monitor running and scheduled task status to track progress and identify issues in your workflow.

Instructions

Check running and scheduled task status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function romm_tasks, which calls the tasks/status endpoint of the RomM API to retrieve and format the status of background tasks.
    async def romm_tasks() -> str:
        """Check running and scheduled task status."""
        data = await _get("tasks/status")
    
        if not isinstance(data, (dict, list)):
            return "No task data available."
    
        if isinstance(data, dict):
            lines = ["Task Status:\n"]
            for task_name, info in data.items():
                if isinstance(info, dict):
                    status = info.get("status", "unknown")
                    last_run = info.get("last_run", "")
                    next_run = info.get("next_run", "")
                    line = f"  {task_name}: {status}"
                    if last_run:
                        line += f" (last: {last_run})"
                    if next_run:
                        line += f" (next: {next_run})"
                    lines.append(line)
                else:
                    lines.append(f"  {task_name}: {info}")
            return "\n".join(lines)
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 states the tool checks task status, implying a read-only operation, but doesn't specify details like whether it requires authentication, how it handles errors, or what the output format includes. This leaves gaps in understanding the tool's behavior.

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 a single, clear sentence with no wasted words. It's front-loaded and efficiently conveys the core function, making it easy to understand at a glance.

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 that there are no parameters and an output schema exists, the description is minimally adequate. However, with no annotations and siblings that might overlap, it lacks context on usage and behavioral traits. It meets basic needs but could be more informative about when and how to use it effectively.

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 information is needed. The description doesn't add any parameter details, which is acceptable here. A baseline of 4 is appropriate since there are no parameters to document.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Check running and scheduled task status' clearly states the tool's function with a specific verb ('Check') and resource ('task status'), but it doesn't distinguish this from sibling tools like 'romm_status' or 'romm_stats', which might also provide status information. The purpose is understandable but lacks sibling differentiation.

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, context, or exclusions, and with siblings like 'romm_status' and 'romm_stats', there's no indication of how this tool differs or when it should be preferred.

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/lodordev/mcp-romm'

If you have feedback or need assistance with the MCP directory API, please join our Discord server