Skip to main content
Glama

romm_recent

Retrieve recently added or updated ROMs from your RomM library to track new content and changes.

Instructions

Recently added or updated ROMs.

limit: Number of results (default 20, max 100).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler for the romm_recent tool, which fetches recently updated ROMs from the API and formats the output.
    async def romm_recent(limit: int = 20) -> str:
        """Recently added or updated ROMs.
    
        limit: Number of results (default 20, max 100).
        """
        limit = min(max(limit, 1), 100)
        params: dict = {
            "limit": limit,
            "offset": 0,
            "order_by": "updated_at",
            "order_dir": "desc",
        }
    
        data = await _get("roms", params=params, long_timeout=True)
    
        items = []
        if isinstance(data, dict):
            items = data.get("items", [])
        elif isinstance(data, list):
            items = data
    
        if not items:
            return "No ROMs found."
    
        lines = [f"Recently updated ROMs ({len(items)}):\n"]
        for i, rom in enumerate(items, 1):
            name = rom.get("name", "Unknown")
            platform = rom.get("platform_display_name") or rom.get("platform_slug", "?")
            updated = rom.get("updated_at", "")
            rom_id = rom.get("id", "?")
    
            line = f"  {i}. {name} [{platform}]"
            lines.append(line)
            if updated:
                lines.append(f"     Updated: {updated}")
            lines.append(f"     ID: {rom_id}")
    
        return "\n".join(lines)
  • server.py:445-445 (registration)
    Tool registration using @mcp.tool() decorator.
    @mcp.tool()
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 a 'limit' parameter with default and max values, which adds some context, but fails to describe key behaviors like pagination, sorting order (e.g., by date), authentication needs, rate limits, or what 'updated' entails. This leaves significant gaps in understanding how the tool operates.

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 highly concise and front-loaded, with the purpose stated first followed by parameter details. Both sentences earn their place by providing essential information without redundancy, making it efficient and well-structured.

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's low complexity (1 parameter) and the presence of an output schema, the description is minimally adequate. However, with no annotations and incomplete behavioral details (e.g., missing time frame for 'recent'), it lacks completeness for optimal agent use, though the output schema mitigates some gaps.

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 description adds meaningful semantics for the single parameter 'limit' by specifying 'Number of results (default 20, max 100),' which goes beyond the input schema's basic type and default. Since schema description coverage is 0%, this compensation is effective, though it does not cover other implicit parameters like time range.

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 states the tool retrieves 'Recently added or updated ROMs,' which provides a clear verb ('retrieves' implied) and resource ('ROMs'). However, it lacks specificity about what 'recently' means (e.g., time frame) and does not distinguish it from sibling tools like 'romm_search' or 'romm_library_items,' making it somewhat vague in context.

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. It does not mention sibling tools or contexts where this tool is preferred, such as for quick updates versus detailed searches. The absence of usage context leaves the agent without direction on selection.

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