Skip to main content
Glama

romm_user_profile

Browse and filter ROMs based on user status categories including favorites, now playing, backlogged, completed, wishlist, and retired.

Instructions

Browse ROMs by user status — favorites, now playing, backlogged, completed.

status_filter: Filter by user status. Options: "now_playing", "backlog", "wishlist", "completed", "retired", "" (shows favorites).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
status_filterNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler implementation for the 'romm_user_profile' MCP tool.
    async def romm_user_profile(status_filter: str = "") -> str:
        """Browse ROMs by user status — favorites, now playing, backlogged, completed.
    
        status_filter: Filter by user status. Options: "now_playing", "backlog",
                       "wishlist", "completed", "retired", "" (shows favorites).
        """
        params: dict = {"limit": 50, "offset": 0, "order_by": "name", "order_dir": "asc"}
    
        if status_filter:
            params["statuses"] = status_filter
        else:
            params["favorite"] = True
    
        data = await _get("roms", params=params, long_timeout=True)
    
        items = []
        if isinstance(data, dict):
            items = data.get("items", [])
        elif isinstance(data, list):
            items = data
    
        label = status_filter.replace("_", " ").title() if status_filter else "Favorites"
    
        if not items:
            return f"No ROMs marked as {label}."
    
        lines = [f"{label} ({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", "?")
            rom_id = rom.get("id", "?")
            user = rom.get("rom_user", {}) or {}
            last_played = user.get("last_played") if isinstance(user, dict) else None
    
            line = f"  {i}. {name} [{platform}]"
            lines.append(line)
            if last_played:
                lines.append(f"     Last played: {last_played}")
            lines.append(f"     ID: {rom_id}")
    
        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 describes a read-only browsing operation, which is clear, but lacks details on permissions, rate limits, pagination, or what the output looks like. For a tool with no annotations, this leaves significant gaps in understanding its behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The description is concise and front-loaded, with the first sentence stating the purpose and the second explaining the parameter. Both sentences earn their place by adding value, though it could be slightly more structured by separating usage notes from parameter details.

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's an output schema (which handles return values), one parameter with good semantic coverage in the description, and no annotations, the description is moderately complete. However, it lacks context on when to use this tool over siblings and behavioral details like pagination or error handling, leaving room for improvement.

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 context for the single parameter 'status_filter' by listing all possible options and explaining that an empty string shows favorites. Since schema description coverage is 0% and there's only one parameter, this compensates well, providing essential semantics beyond the bare schema.

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: 'Browse ROMs by user status' with specific status categories listed. It uses a specific verb ('Browse') and resource ('ROMs'), but doesn't explicitly differentiate from sibling tools like romm_library_items or romm_search, which might also involve browsing ROMs.

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 sibling tools or explain why a user would choose this tool over others like romm_library_items or romm_search, which might serve similar purposes. The only context is implied by the status filtering.

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